All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: John Sigler <linux.kernel@free.fr>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 3/4 RFC] RCU: preemptible RCU
Date: Wed, 8 Aug 2007 06:09:20 -0700	[thread overview]
Message-ID: <20070808130920.GC5024@linux.vnet.ibm.com> (raw)
In-Reply-To: <46B98888.6030600@free.fr>

On Wed, Aug 08, 2007 at 11:10:32AM +0200, John Sigler wrote:
> [ Recipients list trimmed ]
> 
> Paul E. McKenney wrote:
> 
> >This patch was developed as a part of the -rt kernel development and
> >meant to provide better latencies when read-side critical sections of
> >RCU don't disable preemption.  As a consequence of keeping track of RCU
> >readers, the readers have a slight overhead (optimizations in the paper).
> >This implementation co-exists with the "classic" RCU implementations
> >and can be switched to at compiler.
> 
> I cannot parse the last sentence :-)

Oops...  :-/

> Did you mean that this new implementation can be chosen (over the 
> classic implementation) at compile-time?

Yes, via config variables.  CONFIG_CLASSIC_RCU selects the "classic"
RCU implementation, and CONFIG_PREEMPT_RCU selects the preemptible RCU.
CONFIG_PREEMPT_CPU depends on CONFIG_PREEMPT, so that you only are
permitted to specify CONFIG_PREEMPT_RT in preemptible kernels.

						Thanx, Paul

  reply	other threads:[~2007-08-08 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 18:39 [PATCH 0/4 RFC] preemptible RCU Paul E. McKenney
2007-08-07 18:41 ` Paul E. McKenney
2007-08-07 18:43 ` [PATCH 1/4 RFC] RCU: Fix barriers Paul E. McKenney
2007-08-07 18:48 ` [PATCH 3/4 RFC] RCU: preemptible RCU Paul E. McKenney
2007-08-07 19:18   ` Peter Zijlstra
2007-08-08  5:32     ` Paul E. McKenney
2007-08-08  9:10   ` John Sigler
2007-08-08 13:09     ` Paul E. McKenney [this message]
2007-08-07 18:52 ` [PATCH 4/4 RFC] RCU: synchronize_sched() without migration Paul E. McKenney
2007-08-07 19:14   ` Dipankar Sarma
2007-08-07 20:18     ` 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=20070808130920.GC5024@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux.kernel@free.fr \
    /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.