linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Christopher Lameter <cl@linux.com>
Cc: Kirill Tkhai <ktkhai@virtuozzo.com>,
	josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	mingo@redhat.com, penberg@kernel.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	brouer@redhat.com, rao.shoaib@oracle.com
Subject: Re: [PATCH 0/2] rcu: Transform kfree_rcu() into kvfree_rcu()
Date: Wed, 7 Feb 2018 20:09:29 -0800	[thread overview]
Message-ID: <20180208040929.GQ3617@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1802070854080.21329@nuc-kabylake>

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

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2018-02-08  4:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-06 10:19 [PATCH 0/2] rcu: Transform kfree_rcu() into kvfree_rcu() Kirill Tkhai
2018-02-06 10:19 ` [PATCH 1/2] " Kirill Tkhai
2018-02-06 14:34   ` Steven Rostedt
2018-02-06 15:06     ` Kirill Tkhai
2018-02-06 15:49       ` Steven Rostedt
2018-02-06 10:19 ` [PATCH 2/2] mm: Use kvfree_rcu() in update_memcg_params() Kirill Tkhai
2018-02-07  2:17 ` [PATCH 0/2] rcu: Transform kfree_rcu() into kvfree_rcu() Paul E. McKenney
2018-02-07  4:23   ` Matthew Wilcox
2018-02-07  5:02     ` Paul E. McKenney
2018-02-07  7:54       ` Josh Triplett
2018-02-07  8:20         ` Paul E. McKenney
2018-02-07  7:57       ` Kirill Tkhai
2018-02-07  8:31         ` Paul E. McKenney
2018-02-07 13:57           ` Steven Rostedt
2018-02-07 16:18             ` Matthew Wilcox
2018-02-07 16:34               ` Steven Rostedt
2018-02-07 16:45             ` Jesper Dangaard Brouer
2018-02-07 18:10               ` Matthew Wilcox
2018-02-07 18:26                 ` Steven Rostedt
2018-02-08  4:10                   ` Paul E. McKenney
2018-02-22 23:55                 ` Paul E. McKenney
2018-02-08  4:09             ` Paul E. McKenney
2018-02-07 16:47     ` Christopher Lameter
2018-02-07 17:09       ` Steven Rostedt
2018-02-07 17:19         ` Matthew Wilcox
2018-02-07 17:29           ` Steven Rostedt
2018-02-07 17:54             ` Christopher Lameter
2018-02-07 14:55   ` Christopher Lameter
2018-02-08  4:09     ` Paul E. McKenney [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180208040929.GQ3617@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=brouer@redhat.com \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@redhat.com \
    --cc=penberg@kernel.org \
    --cc=rao.shoaib@oracle.com \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).