From: Nikita Danilov <Nikita@Namesys.COM>
To: dipankar@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RCU barrier
Date: Thu, 5 Feb 2004 16:31:29 +0300 [thread overview]
Message-ID: <16418.17841.293641.878787@laputa.namesys.com> (raw)
In-Reply-To: <20040205132809.GE3703@in.ibm.com>
Dipankar Sarma writes:
> This patch introduces a new interface - rcu_barrier() which waits
> until all the RCUs queued until this call have been completed.
> Nikita asked for this quite a while ago for reiser4 jnodes.
> Sorry Nikita, if you are still using RCU in new reiserfs,
> you don't need to use your own logic for this now. Just
> call rcu_barrier() during umount.
>
> If Nikita or other users use it, then I would like to push for
> including this.
Yes, we are still using RCU in the reiser4 (bravely). rcu_barrier()
would allow us to get rid of some really ugly code.
>
> Thanks
> Dipankar
>
Nikita.
next prev parent reply other threads:[~2004-02-05 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 13:28 Dipankar Sarma
2004-02-05 13:31 ` Nikita Danilov [this message]
2004-02-05 13:39 ` Dipankar Sarma
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=16418.17841.293641.878787@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=dipankar@in.ibm.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
all inboxes | Powered by JetHome®