Re: [RFC PATCH] rcu: don't ignore preempt_disable() in the idle loop

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Frederic Weisbecker
Date: Tuesday, March 9, 2010 - 5:54 pm

On Tue, Mar 09, 2010 at 07:13:27PM +0800, Lai Jiangshan wrote:



This is neat. But I wonder about something. It means that in most of
the idle loop, we won't be able to schedule the rcu callbacks
So if I understand well, this is going to needlessly delay
rcu callbacks for no strong reason most of the time. I'm not sure
if this is going to have any bad impact, but if so may be
do we want this as a feature, and check we currently have
running users of this feature (I only have function tracers in mind,
may be I'm missing some others). Altough I wonder how racy such
a check could be. At least we can make it a CONFIG.

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [RFC PATCH] rcu: don't ignore preempt_disable() in the ..., Frederic Weisbecker, (Tue Mar 9, 5:54 pm)