From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, 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,
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: Re: [PATCH tip/core/rcu 0/2] v2 Add callback-free CPUs
Date: Wed, 31 Oct 2012 00:44:02 -0700 [thread overview]
Message-ID: <20121031074402.GV3027@linux.vnet.ibm.com> (raw)
In-Reply-To: <1351668321.4047.39.camel@twins>
On Wed, Oct 31, 2012 at 08:25:21AM +0100, Peter Zijlstra wrote:
> On Tue, 2012-10-30 at 20:45 -0700, Paul E. McKenney wrote:
> > 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.
>
> How much pain to make that dynamically configurable?
A fair amount of pain, though I do hope to make it runtime configurable
at some point. Known problems include races between changes in the
nocb configuration, rcu_barrier(), grace-period initialization, and
CPU hotplug. Should be solvable, but want to get the other bugs out of
the way first.
Thanx, Paul
prev parent reply other threads:[~2012-10-31 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 3:45 [PATCH tip/core/rcu 0/2] v2 Add callback-free CPUs Paul E. McKenney
2012-10-31 3:46 ` [PATCH tip/core/rcu 1/2] rcu: " 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 [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=20121031074402.GV3027@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