All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: 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: [PATCH 0/4 RFC] preemptible RCU
Date: Tue, 7 Aug 2007 11:39:46 -0700	[thread overview]
Message-ID: <20070807183946.GA32110@linux.vnet.ibm.com> (raw)

Hello!

This patchset is an update of that posted by Dipankar last January
(http://lkml.org/lkml/2007/1/15/133).  This is work in progress, not yet
ready for inclusion.  It passes rcutorture on i386, x86_64, and ppc64
boxes as well as kernbench, so should be safe for experimentation.  As
with Dipankar's previous post, this variant of preemptible rcu_read_lock()
and rcu_read_unlock may be invoked from NMI/SMI handlers, and do not
contain any heavyweight atomic operations or memory barriers (although
they do still momentarily disable IRQs).  This patchset features
a fully parallel grace-period computation, which will become increasingly
important with upcoming multicore/multi-threaded CPUs.  In addition,
this patchset provides a preemptible-RCU variant of synchronize_sched()
that avoids the previous deadlock with CPU hotplug -- this variant may
eventually prove unnecessary, but is offered in the spirit of separating
concerns.

Next steps:  (1) Integrate with CPU hotplug.  (2) Re-merge RCU priority
boosting.  (3) Fix some naming issues.  Longer term work includes
optimized dyntick operation and eliminating the interrupt disabling
in rcu_read_lock() and rcu_read_unlock().

						Thanx, Paul

             reply	other threads:[~2007-08-07 18:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 18:39 Paul E. McKenney [this message]
2007-08-07 18:41 ` [PATCH 0/4 RFC] preemptible RCU 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
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=20070807183946.GA32110@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --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=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 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.