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@efficios.com,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu, patches@linaro.org, joe.korty@ccur.com
Subject: [PATCH tip/core/rcu 0/2] v2 Add callback-free CPUs
Date: Tue, 30 Oct 2012 20:45:52 -0700 [thread overview]
Message-ID: <20121031034552.GA1999@linux.vnet.ibm.com> (raw)
Hello!
RCU callback execution can add significant OS jitter and also can
degrade scheduling latency. This commit therefore adds the ability
for selected CPUs ("rcu_nocbs=" boot parameter) to have their callbacks
offloaded to kthreads, inspired by Joe Korty's and Jim Houston's JRCU.
If the "rcu_nocb_poll" boot parameter is also specified, these kthreads
will do polling, removing the need for the offloaded CPUs to do wakeups.
At least one CPU must be doing normal callback processing: currently CPU
0 cannot be selected as a no-CBs CPU. In addition, attempts to offline
the last normal-CBs CPU will fail.
Changes since v1 (https://lkml.org/lkml/2012/9/5/572):
1. Contains fixes for a few problems located by Fengguang Wu's
kbuild test robot.
2. Counters are now atomic_long_t rather than atomic_t, as
suggested by Peter Zijlstra.
3. The rcu_nocbs= kernel boot parameter is now documented.
4. Fixed a bug introduced by commit c96ea7cf (Avoid spurious
RCU CPU stall warnings) that resulted in boot-time NULL-pointer
dereferences (reported by Paul Gortmaker).
4. Account for normal and offloaded callbacks separately, so that
offloading is represented in debugfs output.
The patches in this series are as follows:
1. Offload RCU callbacks based on boot-time kernel parameter.
2. Account for normal and offloaded callbacks separately, so that
offloading is represented in debugfs output.
Thanx, Paul
b/Documentation/kernel-parameters.txt | 5
b/include/trace/events/rcu.h | 1
b/init/Kconfig | 19 +
b/kernel/rcutree.c | 63 ++++-
b/kernel/rcutree.h | 48 ++++
b/kernel/rcutree_plugin.h | 399 +++++++++++++++++++++++++++++++++-
b/kernel/rcutree_trace.c | 12 -
7 files changed, 528 insertions(+), 19 deletions(-)
next reply other threads:[~2012-10-31 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 3:45 Paul E. McKenney [this message]
2012-10-31 3:46 ` [PATCH tip/core/rcu 1/2] rcu: Add callback-free CPUs Paul E. McKenney
2012-10-31 3:46 ` [PATCH tip/core/rcu 2/2] rcu: Separate accounting of callbacks from " Paul E. McKenney
2012-10-31 14:10 ` [PATCH tip/core/rcu 1/2] rcu: Add " Frederic Weisbecker
2012-11-02 18:41 ` Paul E. McKenney
2012-11-02 21:21 ` Frederic Weisbecker
2012-10-31 7:25 ` [PATCH tip/core/rcu 0/2] v2 " Peter Zijlstra
2012-10-31 7:44 ` 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=20121031034552.GA1999@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=joe.korty@ccur.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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