[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180207122910.1a91a48e@gandalf.local.home>
Date: Wed, 7 Feb 2018 12:29:10 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Christopher Lameter <cl@...ux.com>,
"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 09:19:36 -0800
Matthew Wilcox <willy@...radead.org> wrote:
> > Please no, I hate subtle internal decisions like this. It makes
> > debugging much more difficult, when allocating dynamic sized variables.
> > When something works at one size but not the other.
>
> You know we already have kvmalloc()?
Yes, and the name suggests exactly what it does. It has both "k" and
"v" which tells me that if I use it it could be one or the other.
But a generic "malloc" or "free" that does things differently depending
on the size is a different story.
-- Steve
Powered by blists - more mailing lists