From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Josh Triplett <josh@joshtriplett.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,
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
Subject: Re: [PATCH tip/core/rcu 1/1] Tiny RCU changes for 3.9
Date: Thu, 10 Jan 2013 12:18:32 -0800 [thread overview]
Message-ID: <20130110201832.GV2491@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130108042249.GB12974@leaf>
On Mon, Jan 07, 2013 at 08:22:50PM -0800, Josh Triplett wrote:
> On Mon, Jan 07, 2013 at 02:19:15PM -0800, Paul E. McKenney wrote:
> > On Mon, Jan 07, 2013 at 09:56:06AM -0800, Josh Triplett wrote:
> > > On Mon, Jan 07, 2013 at 08:57:48AM -0800, Paul E. McKenney wrote:
> > > > On Mon, Jan 07, 2013 at 07:58:10AM -0800, Josh Triplett wrote:
> > > > > This patch seems reasonable to me, but the repeated use of #if
> > > > > defined(CONFIG_SMP) || defined(CONFIG_RCU_TRACE) seems somewhat
> > > > > annoying, and fragile if you ever decide to change the conditions. How
> > > > > about defining an appropriate symbol in Kconfig for stall warnings, and
> > > > > using that?
> > > >
> > > > But I only just removed the config option for SMP RCU stall warnings. ;-)
> > > >
> > > > But I must agree that "defined(CONFIG_SMP) || defined(CONFIG_RCU_TRACE)"
> > > > is a bit obscure. The rationale is that RCU stall warnings are
> > > > unconditionally enabled in SMP kernels, but don't want to be in
> > > > TINY_RCU kernels due to size constraints. I therefore put it under
> > > > CONFIG_RCU_TRACE, which also contains other TINY_RCU debugging-style
> > > > options. Would adding a comment to this effect help?
> > >
> > > I understand the rationale; I just think it would become clearer if you
> > > added an internal-only Kconfig symbol selected in both cases and change
> > > the conditionals to use that.
> >
> > My concern was that this would confuse people into thinking that the
> > code under those #ifdefs was all the stall-warning code that there was.
> >
> > I suppose this could be forestalled with a suitably clever name...
> > CONFIG_RCU_CPU_STALL_TINY_TOO? Better names?
>
> How about CONFIG_RCU_STALL_COMMON, with associated help text saying
> "include the stall-detection code common to both rcutree and rcutiny"?
Sold!!! Especially given that I am creating the commit to allow
TREE_PREEMPT_RCU to be used on UP systems with an eye towards getting
rid of TINY_PREEMPT_RCU. ;-)
Thanx, Paul
prev parent reply other threads:[~2013-01-10 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 17:50 [PATCH tip/core/rcu 1/1] Tiny RCU changes for 3.9 Paul E. McKenney
2013-01-07 15:58 ` Josh Triplett
2013-01-07 16:57 ` Paul E. McKenney
2013-01-07 17:56 ` Josh Triplett
2013-01-07 22:19 ` Paul E. McKenney
2013-01-08 4:22 ` Josh Triplett
2013-01-10 20:18 ` 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=20130110201832.GV2491@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=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 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.