From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com,
dipankar@in.ibm.com, akpm@linux-foundation.org,
mathieu.desnoyers@polymtl.ca, josh@joshtriplett.org,
dvhltc@us.ibm.com, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu
Subject: Re: [PATCH tip/core/rcu 0/3] Cleanups/bugfixes for large systems and TREE_PREEMPT_RCU
Date: Sat, 19 Sep 2009 08:55:23 +0200 [thread overview]
Message-ID: <20090919065523.GA17617@elte.hu> (raw)
In-Reply-To: <20090918164955.GA22272@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> This set of patches does some cleanups and fixes a bug that prevents
> TREE_PREEMPT_RCU from running reliably on large systems (more than 64
> CPUs, or on 32-bit systems, more than 32 CPUs). The patches are as
> follows:
>
> 1. Add WARN_ON_ONCE() consistency checks to catch bugs. These
> are all on slowpaths, so are appropriate for production use.
>
> 2. Apply the results of a code walkthrough of rcutree_plugin.h.
> This includes a fix for a theoretical race that could result in
> excessively long RCU grace periods, or perhaps even hangs/OOMs.
>
> 3. Fix a bug introduced in a bugfix commit #de078d875 that caused
> large systems to only partially initialize the fields in the
> rcu_node tree. TREE_RCU doesn't care about any of these fields,
> which explains why only TREE_PREEMPT_RCU was broken.
>
> With these fixes, large systems using TREE_PREEMPT_RCU pass moderate
> rcutorture runs (but with Josh Triplett's mods that force frequent
> preemption within RCU read-side critical sections). I am sure that
> there are more bugs, but these fixes get things much closer.
>
> b/kernel/rcutree.c | 13 +++++++++----
> b/kernel/rcutree_plugin.h | 21 ++++++++++++++-------
> kernel/rcutree.c | 38 +++++++++-----------------------------
> kernel/rcutree_plugin.h | 16 +++++++++-------
> 4 files changed, 41 insertions(+), 47 deletions(-)
Thanks Paul, applied them to tip:core/urgent.
Ingo
prev parent reply other threads:[~2009-09-19 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 16:49 [PATCH tip/core/rcu 0/3] Cleanups/bugfixes for large systems and TREE_PREEMPT_RCU Paul E. McKenney
2009-09-18 16:50 ` [PATCH tip/core/rcu 1/3] Add WARN_ON_ONCE() consistency checks covering state transitions Paul E. McKenney
2009-09-19 7:58 ` [tip:core/urgent] rcu: " tip-bot for Paul E. McKenney
2009-09-18 16:50 ` [PATCH tip/core/rcu 2/3] Apply results of code inspection of kernel/rcutree_plugin.h Paul E. McKenney
2009-09-18 16:58 ` Daniel Walker
2009-09-18 17:00 ` Peter Zijlstra
[not found] ` <1253293408.7060.47.camel@desktop>
2009-09-18 17:04 ` Peter Zijlstra
2009-09-18 17:08 ` Daniel Walker
2009-09-18 17:22 ` Paul E. McKenney
2009-09-18 17:56 ` Daniel Walker
2009-09-19 7:58 ` [tip:core/urgent] rcu: " tip-bot for Paul E. McKenney
2009-09-18 16:50 ` [PATCH tip/core/rcu 3/3] Fix thinko in commit #de078d875, actually initialize full tree Paul E. McKenney
2009-09-19 7:59 ` [tip:core/urgent] rcu: Fix thinko, " tip-bot for Paul E. McKenney
2009-09-19 6:55 ` Ingo Molnar [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=20090919065523.GA17617@elte.hu \
--to=mingo@elte.hu \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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