From: Keenan Pepper <keenanpepper@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: synchronize_rcu vs. rcu_barrier
Date: Sun, 07 Aug 2005 17:52:46 -0400 [thread overview]
Message-ID: <42F682AE.2010803@gmail.com> (raw)
In-Reply-To: <42F66E81.2020807@gmail.com>
> What's the difference between synchronize_rcu() and rcu_barrier() (new
> function used only by reiser4 code)? From the scant documentation it
> seems like they do the same thing.
I'm now happily running 2.6.13-rc4-rt-v0.7.52-14-reiser4 which I compiled by adding
#define rcu_barrier synchronize_rcu
so there must not be that much difference =) (at least on UP, that is).
Keenan
prev parent reply other threads:[~2005-08-07 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 20:26 synchronize_rcu vs. rcu_barrier Keenan Pepper
2005-08-07 21:52 ` Keenan Pepper [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=42F682AE.2010803@gmail.com \
--to=keenanpepper@gmail.com \
--cc=linux-kernel@vger.kernel.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