From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josh@joshtriplett.org, dvhltc@us.ibm.com, niv@us.ibm.com,
tglx@linutronix.de, peterz@infradead.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com
Subject: Re: [PATCH RFC tip/core/rcu] accelerate grace period if last non-dynticked CPU
Date: Wed, 27 Jan 2010 06:11:10 -0800 [thread overview]
Message-ID: <20100127141109.GA21087@linux.vnet.ibm.com> (raw)
In-Reply-To: <1264432323.31321.412.camel@gandalf.stny.rr.com>
On Mon, Jan 25, 2010 at 10:12:03AM -0500, Steven Rostedt wrote:
> On Sun, 2010-01-24 at 19:48 -0800, Paul E. McKenney wrote:
>
> > +/*
> > + * Check to see if any future RCU-related work will need to be done
> > + * by the current CPU, even if none need be done immediately, returning
> > + * 1 if so. This function is part of the RCU implementation; it is -not-
> > + * an exported member of the RCU API.
> > + *
> > + * Because we are not supporting preemptible RCU, attempt to accelerate
> > + * any current grace periods so that RCU no longer needs this CPU, but
> > + * only if all other CPUs are already in dynticks-idle mode. This will
> > + * allow the CPU cores to be powered down immediately, as opposed to after
> > + * waiting many milliseconds for grace periods to elapse.
> > + */
> > +int rcu_needs_cpu(int cpu)
> > +{
> > + int c = 1;
> > + int i;
> > + int thatcpu;
> > +
> > + /* Don't bother unless we are the last non-dyntick-idle CPU. */
> > + for_each_cpu(thatcpu, nohz_cpu_mask)
> > + if (thatcpu != cpu)
> > + return rcu_needs_cpu_quick_check(cpu);
> > +
> > + /* Try to push remaining RCU-sched and RCU-bh callbacks through. */
> > + for (i = 0; i < RCU_NEEDS_CPU_FLUSHES && c; i++) {
> > + c = 0;
> > + if (per_cpu(rcu_sched_data, cpu).nxtlist) {
> > + c = 1;
> > + rcu_sched_qs(cpu);
> > + force_quiescent_state(&rcu_sched_state, 0);
> > + __rcu_process_callbacks(&rcu_sched_state,
> > + &per_cpu(rcu_sched_data, cpu));
>
> > + }
> > + if (per_cpu(rcu_bh_data, cpu).nxtlist) {
> > + c = 1;
> > + rcu_bh_qs(cpu);
> > + force_quiescent_state(&rcu_bh_state, 0);
> > + __rcu_process_callbacks(&rcu_bh_state,
> > + &per_cpu(rcu_bh_data, cpu));
> > + }
> > + }
> > +
> > + /* If RCU callbacks are still pending, RCU still needs this CPU. */
> > + return c;
>
> What happens if the last loop pushes out all callbacks? Then we would be
> returning 1 when we could really be returning 0. Wouldn't a better
> answer be:
>
> return per_cpu(rcu_sched_data, cpu).nxtlist ||
> per_cpu(rcu_bh_data, cpu).nxtlist;
Good point!!!
Or I can move the assignment to "c" to the end of each branch of the
"if" statement, and do something like the following:
c = !!per_cpu(rcu_sched_data, cpu).nxtlist;
But either way, you are right, it does not make sense to go to all the
trouble of forcing a grace period and then failing to take advantage
of it.
Thanx, Paul
next prev parent reply other threads:[~2010-01-27 14:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 3:48 [PATCH RFC tip/core/rcu] accelerate grace period if last non-dynticked CPU Paul E. McKenney
2010-01-25 12:28 ` Lai Jiangshan
2010-01-25 12:35 ` Peter Zijlstra
2010-01-25 15:08 ` Steven Rostedt
2010-01-27 5:17 ` Paul E. McKenney
2010-01-25 15:12 ` Steven Rostedt
2010-01-27 14:11 ` Paul E. McKenney [this message]
2010-01-27 14:52 ` Steven Rostedt
2010-01-26 21:30 ` Andi Kleen
2010-01-26 23:55 ` Mathieu Desnoyers
2010-01-27 5:21 ` Paul E. McKenney
2010-01-27 5:20 ` Paul E. McKenney
2010-01-27 9:43 ` Andi Kleen
2010-01-27 9:50 ` Peter Zijlstra
2010-01-27 10:00 ` Andi Kleen
2010-01-27 10:04 ` Paul E. McKenney
2010-01-27 11:39 ` Nick Piggin
2010-01-27 11:59 ` Paul E. McKenney
2010-01-27 10:01 ` Paul E. McKenney
2010-01-27 10:13 ` Andi Kleen
2010-01-27 11:44 ` Paul E. McKenney
2010-01-27 12:11 ` Andi Kleen
2010-01-27 13:23 ` Paul E. McKenney
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=20100127141109.GA21087@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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