From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: dipankar@in.ibm.com, shemminger@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] Updated RCU documentation improvement
Date: Wed, 4 Aug 2004 16:33:57 -0700 [thread overview]
Message-ID: <20040804233357.GE1239@us.ibm.com> (raw)
In-Reply-To: <1091657826.2964.3.camel@laptop.cunninghams>
On Thu, Aug 05, 2004 at 08:17:07AM +1000, Nigel Cunningham wrote:
> Hi.
>
> What does RCU stand for? I haven't looked very hard, but all I've seen
> is RCU, and not an expansion of the abbreviation.
>
> Regards,
Hello, Nigel,
RCU stands for "read-copy update". The rationale behind the name
is that readers proceed concurrently with updaters, and updaters
must make copies in order for complex updates to appear atomic
to readers.
That said, most uses of RCU simply add and delete items. Very
few uses do in-place RCU-protected updates.
Thanx, Paul
prev parent reply other threads:[~2004-08-04 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 14:16 [RFC][PATCH] Updated RCU documentation improvement Paul E. McKenney
2004-08-04 22:17 ` Nigel Cunningham
2004-08-04 23:33 ` 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=20040804233357.GE1239@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=shemminger@osdl.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