[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1802071152580.22710@nuc-kabylake>
Date: Wed, 7 Feb 2018 11:54:22 -0600 (CST)
From: Christopher Lameter <cl@...ux.com>
To: Steven Rostedt <rostedt@...dmis.org>
cc: Matthew Wilcox <willy@...radead.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Kirill Tkhai <ktkhai@...tuozzo.com>, josh@...htriplett.org,
mathieu.desnoyers@...icios.com, jiangshanlai@...il.com,
mingo@...hat.com, penberg@...nel.org, rientjes@...gle.com,
iamjoonsoo.kim@....com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
brouer@...hat.com, rao.shoaib@...cle.com
Subject: Re: [PATCH 0/2] rcu: Transform kfree_rcu() into kvfree_rcu()
On Wed, 7 Feb 2018, Steven Rostedt wrote:
> But a generic "malloc" or "free" that does things differently depending
> on the size is a different story.
They would not be used for cases with special requirements but for the
throwaway allows where noone cares about these details. Its just a
convenience for the developers that do not need to be bothered with too
much detail because they are not dealing with codepaths that have special
requirements.
Powered by blists - more mailing lists