From: Manfred Spraul <manfred@colorfullife.com>
To: paulmck@linux.vnet.ibm.com
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dipankar Sarma <dipankar@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC PATCH] rcu: introduce kfree_rcu()
Date: Fri, 19 Sep 2008 18:03:20 +0200 [thread overview]
Message-ID: <48D3CD48.4090701@colorfullife.com> (raw)
In-Reply-To: <20080918174619.GA28186@linux.vnet.ibm.com>
Paul E. McKenney wrote:
> The rcu_barrier() family of functions registers a callback on each CPU,
> and waits until all these callbacks have been invoked. The CPU offlining
> process preserves the order of the callbacks that were registered on a
> given CPU. Thus, when rcu_barrier() returns, all RCU callbacks previously
> registered are guaranteed to have already been invoked, regardless of
> what CPUs might have been offlined and onlined in the meantime.
>
>
You are right: I mixed up rcu_barrier() and synchronize_rcu().
--
Manfred
next prev parent reply other threads:[~2008-09-19 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 4:18 [RFC PATCH] rcu: introduce kfree_rcu() Lai Jiangshan
2008-09-18 4:37 ` Andrew Morton
2008-09-18 16:52 ` Manfred Spraul
2008-09-19 2:31 ` Lai Jiangshan
2008-09-18 6:44 ` Paul E. McKenney
2008-09-18 8:59 ` Lai Jiangshan
2008-09-18 17:15 ` Paul E. McKenney
2008-09-18 16:56 ` Manfred Spraul
2008-09-18 17:46 ` Paul E. McKenney
2008-09-19 16:03 ` Manfred Spraul [this message]
2008-09-19 1:04 ` Lai Jiangshan
2008-09-19 3:58 ` Paul E. McKenney
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=48D3CD48.4090701@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.