[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180208040929.GQ3617@linux.vnet.ibm.com>
Date: Wed, 7 Feb 2018 20:09:29 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Christopher Lameter <cl@...ux.com>
Cc: Kirill Tkhai <ktkhai@...tuozzo.com>, josh@...htriplett.org,
rostedt@...dmis.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, Feb 07, 2018 at 08:55:47AM -0600, Christopher Lameter wrote:
> On Tue, 6 Feb 2018, Paul E. McKenney wrote:
>
> > So it is OK to kvmalloc() something and pass it to either kfree() or
> > kvfree(), and it had better be OK to kvmalloc() something and pass it
> > to kvfree().
>
> kvfree() is fine but not kfree().
Ah, even more fun, then! ;-)
Thanx, Paul
Powered by blists - more mailing lists