public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: "M. Fioretti" <m.fioretti@inwind.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6: new features and older computers
Date: Thu, 16 Oct 2003 10:17:11 -0700	[thread overview]
Message-ID: <20031016171711.GA1676@us.ibm.com> (raw)
In-Reply-To: <20031006052154.GB26388@inwind.it>

Hello, Marco,

I can help with one of these...

On Mon, Oct 06, 2003 at 07:21:54AM +0200, M. Fioretti wrote:
> 4) What is RCU and which kind of performances it will improve

RCU is a locking mechanism that is useful primarily for read-mostly
data structures.  It can be thought of as a reader-writer lock in which
the readers need not actually do anything, which means that you can
get substantial performance improvements in read-mostly situations.
The writers must perform updates in a careful manner to avoid messing
up the readers.  In particular, if a writer removes an element from a
list, it must wait for a "grace period" before freeing up the element,
since readers might still be referencing it.  RCU provides primitives
that wait for grace periods to elapse.

The best introduction to RCU is probably:

	http://www.linuxjournal.com/article.php?sid=6993

More information on RCU, including performance comparisons in
the Linux kernel may be found at:

	http://www.rdrop.com/users/paulmck/rclock/

					Thanx, Paul

      reply	other threads:[~2003-10-17  0:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06  5:21 Kernel 2.6: new features and older computers M. Fioretti
2003-10-16 17:17 ` 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=20031016171711.GA1676@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.fioretti@inwind.it \
    /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