[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080925140506.GA6725@linux.vnet.ibm.com>
Date: Thu, 25 Sep 2008 07:05:06 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org, cl@...ux-foundation.org,
akpm@...ux-foundation.org, manfred@...orfullife.com,
dipankar@...ibm.com, josht@...ux.vnet.ibm.com, schamp@....com,
niv@...ibm.com, dvhltc@...ibm.com, ego@...ibm.com,
laijs@...fujitsu.com, rostedt@...dmis.org, peterz@...radead.org,
penberg@...helsinki.fi, andi@...stfloor.org, tglx@...utronix.com
Subject: Re: [PATCH, RFC] v6 scalable classic RCU implementation
On Thu, Sep 25, 2008 at 09:26:07AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
>
> > +config RCU_CPU_STALL_DETECTOR
> > + bool "Check for stalled CPUs delaying RCU grace periods"
> > + depends on CLASSIC_RCU || TREE_RCU
> > + default n
> > + help
> > + This option causes RCU to printk information on which
> > + CPUs are delaying the current grace period, but only when
> > + the grace period extends for excessive time periods.
> > +
> > + Say Y if you want RCU to perform such checks.
> > +
> > + Say N if you are unsure.
>
> could you please send this bit separately, even if rcutree isnt finished
> yet? Seems like a quite useful debug feature.
Good point -- I guess I do need to implement the CLASSIC_RCU piece of
this in any case.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists