From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
mingo@elte.hu, akpm@linux-foundation.org, dipankar@in.ibm.com,
josht@linux.vnet.ibm.com, tytso@us.ibm.com, dvhltc@us.ibm.com,
tglx@linutronix.de
Subject: Re: [PATCH 3/4 RFC] RCU: preemptible RCU
Date: Tue, 07 Aug 2007 21:18:29 +0200 [thread overview]
Message-ID: <1186514309.11797.171.camel@lappy> (raw)
In-Reply-To: <20070807184812.GC10068@linux.vnet.ibm.com>
On Tue, 2007-08-07 at 11:48 -0700, Paul E. McKenney wrote:
> This patch implements a new version of RCU which allows its read-side
> critical sections to be preempted. It uses a set of counter pairs
> to keep track of the read-side critical sections and flips them
> when all tasks exit read-side critical section. The details
> of this implementation can be found in this paper -
>
> http://www.rdrop.com/users/paulmck/RCU/OLSrtRCU.2006.08.11a.pdf
>
> 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.
>
> Also includes RCU tracing summarized in debugfs and RCU_SOFTIRQ for
> the preemptible variant of RCU.
Whickedly complex but very cool stuff!
Unfortunately I have nothing to contribute other than praise at the
complex yet elegant way you dodged the need for synchronisation.
next prev parent reply other threads:[~2007-08-07 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 18:39 [PATCH 0/4 RFC] " 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 [this message]
2007-08-08 5:32 ` Paul E. McKenney
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=1186514309.11797.171.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josht@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=tytso@us.ibm.com \
/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
Powered by JetHome