From: Steven Rostedt <rostedt@goodmis.org>
To: John Kacur <jkacur@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 3/3] rcu: Drive configuration directly from SMP and PREEMPT
Date: Mon, 21 Nov 2011 11:10:00 -0500 [thread overview]
Message-ID: <1321891800.20742.11.camel@frodo> (raw)
In-Reply-To: <1321707028-12487-4-git-send-email-jkacur@redhat.com>
On Sat, 2011-11-19 at 13:50 +0100, John Kacur wrote:
> From: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> This commit eliminates the possibility of running TREE_PREEMPT_RCU
> when SMP=n and of running TINY_RCU when PREEMPT=y. People who really
> want these combinations can hand-edit init/Kconfig, but eliminating
> them as choices for production systems reduces the amount of testing
> required. It will also allow cutting out a few #ifdefs.
>
> Note that running TREE_RCU and TINY_RCU on single-CPU systems using
> SMP-built kernels is still supported.
With this patch, I can see the need for the first patch (although
there's things broken even for that), but is this really a stable fix?
This looks more of an added feature than a bug fix. It's a bug fix if we
consider running tree_rcu on UP a bug. Or better stated, will it break
anything if we do that?
-- Steve
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>
> commit 8008e129dc90ff4f7a56cb033d6bd042afe3ed52 upstream
> Cherry-picked for v3.0-rt and fixed-up merge conflicts
> Note: This makes the depends lines for these options in init/Kconfig for v3.0-rt
> match those for v3.2-rc2-rt3
> Signed-off-by: John Kacur <jkacur@redhat.com>
> ---
> init/Kconfig | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 89e40a4..5c1147e 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -391,7 +391,7 @@ config TREE_RCU
>
> config TREE_PREEMPT_RCU
> bool "Preemptible tree-based hierarchical RCU"
> - depends on PREEMPT
> + depends on PREEMPT && SMP
> help
> This option selects the RCU implementation that is
> designed for very large SMP systems with hundreds or
> @@ -401,7 +401,7 @@ config TREE_PREEMPT_RCU
>
> config TINY_RCU
> bool "UP-only small-memory-footprint RCU"
> - depends on !SMP && !PREEMPT_RT_FULL
> + depends on !PREEMPT && !SMP
> help
> This option selects the RCU implementation that is
> designed for UP systems from which real-time response
> @@ -410,7 +410,7 @@ config TINY_RCU
>
> config TINY_PREEMPT_RCU
> bool "Preemptible UP-only small-memory-footprint RCU"
> - depends on !SMP && PREEMPT && !PREEMPT_RT_FULL
> + depends on PREEMPT && !SMP
> help
> This option selects the RCU implementation that is designed
> for real-time UP systems. This option greatly reduces the
next prev parent reply other threads:[~2011-11-21 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 12:50 [PATCH 0/3] Suggested patches for v3.0.9-rt26 John Kacur
2011-11-19 12:50 ` [PATCH 1/3] rcu-more-fallout.patch John Kacur
2011-11-21 16:04 ` Steven Rostedt
2011-11-19 12:50 ` [PATCH 2/3] sysctl-include-fix.patch John Kacur
2011-11-21 16:06 ` Steven Rostedt
2011-11-19 12:50 ` [PATCH 3/3] rcu: Drive configuration directly from SMP and PREEMPT John Kacur
2011-11-21 16:10 ` Steven Rostedt [this message]
2011-11-21 23:18 ` John Kacur
2011-11-21 23:46 ` Steven Rostedt
2011-11-21 23:51 ` John Kacur
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=1321891800.20742.11.camel@frodo \
--to=rostedt@goodmis.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).