From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, 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, dhowells@redhat.com
Subject: [PATCH tip/core/rcu 0/2] rcu: v2: more review feedback
Date: Mon, 28 Sep 2009 07:45:51 -0700 [thread overview]
Message-ID: <20090928144551.GA20704@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090927064753.GA9394@linux.vnet.ibm.com>
This patchset applies the last of the review comments:
o Whitespace fixes, updated comments, and code movement.
o Improve an existing abstraction and introduce two additional
abstractions for traversing the rcu_node tree.
Change since v1 (http://lkml.org/lkml/2009/9/27/17):
o Update second patch's changelog
Issues remaining:
o I can force hangs given sufficient rcutorture testing in
conjunction with random CPU-hotplug operations. I am working
on a simpler interface between RCU and CPU hotplug that I
believe will clear this up.
o TREE_PREEMPT_RCU currently uses the TREE_RCU variant of
synchronize_rcu_expedited, which is wrong. I am working on
an expedited variant for TREE_PREEMPT_RCU, but will fall
back on synchronize_rcu() for the short term if it gives me
much trouble.
o The IPI hyperactivity from call_rcu() noted by Nick Piggin.
I believe I have identified a clean design for a fix for this.
o Make RCU less dependent on IPIs for forcing grace periods
(but this might be best deferred to 2.6.33).
o RCU priority boosting (2.6.33!).
o TINY_PREEMPT_RCU (2.6.33!).
o Squeeze another 400 bytes or so out of TINY_RCU (2.6.33!).
b/include/linux/rcupdate.h | 14 +++++------
b/kernel/rcutree.c | 11 ++++-----
b/kernel/rcutree.h | 12 ++++++++++
b/kernel/rcutree_plugin.h | 5 ----
kernel/rcutree.c | 53 +++++++++++++++++++++++----------------------
5 files changed, 52 insertions(+), 43 deletions(-)
next prev parent reply other threads:[~2009-09-28 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-27 6:47 [PATCH tip/core/rcu 0/2] rcu: more review feedback Paul E. McKenney
2009-09-27 6:49 ` [PATCH tip/core/rcu 1/2] rcu: Apply review feedback from Josh Triplett, part 3 Paul E. McKenney
2009-09-27 15:41 ` Josh Triplett
2009-09-27 6:49 ` [PATCH tip/core/rcu 2/2] rcu: Apply review feedback from Josh Triplett, part 4 Paul E. McKenney
2009-09-27 15:31 ` Josh Triplett
2009-09-28 4:35 ` Paul E. McKenney
2009-09-28 14:45 ` Paul E. McKenney [this message]
2009-09-28 14:46 ` [PATCH tip/core/rcu 1/2] rcu: Apply review feedback from Josh Triplett, part 3 Paul E. McKenney
2009-09-28 15:55 ` [tip:core/rcu] rcu: Clean up code based on " tip-bot for Paul E. McKenney
2009-10-05 19:09 ` tip-bot for Paul E. McKenney
2009-09-28 14:46 ` [PATCH tip/core/rcu 2/2] rcu: Apply review feedback from Josh Triplett, part 4 Paul E. McKenney
2009-09-28 15:55 ` [tip:core/rcu] rcu: Clean up code based on " tip-bot for Paul E. McKenney
2009-10-05 19:10 ` tip-bot for Paul E. McKenney
2009-09-28 15:53 ` [PATCH tip/core/rcu 0/2] rcu: v2: more review feedback Ingo Molnar
2009-09-28 16:09 ` Josh Triplett
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=20090928144551.GA20704@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--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=mingo@elte.hu \
--cc=niv@us.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 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.