From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] sched: fix clear NOHZ_BALANCE_KICK
Date: Tue, 4 Jun 2013 13:15:10 +0200 [thread overview]
Message-ID: <20130604111510.GO8923@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20130604102620.GB14012@somewhere>
On Tue, Jun 04, 2013 at 12:26:22PM +0200, Frederic Weisbecker wrote:
> On Tue, Jun 04, 2013 at 11:36:11AM +0200, Peter Zijlstra wrote:
> >
> > The best I can seem to come up with is something like the below; but I think
> > its ghastly. Surely we can do something saner with that bit.
> >
> > Having to clear it at 3 different places is just wrong.
>
> We could clear the flag early in scheduler_ipi() and set some
> specific value in rq->idle_balance that tells we want nohz idle
> balancing from the softirq, something like this untested:
Yeah, I suppose something like that is a little better.. a few nits
though:
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 58453b8..330136b 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -630,15 +630,14 @@ void wake_up_nohz_cpu(int cpu)
> wake_up_idle_cpu(cpu);
> }
>
> -static inline bool got_nohz_idle_kick(void)
> +static inline bool got_nohz_idle_kick(int cpu)
> {
> - int cpu = smp_processor_id();
> - return idle_cpu(cpu) && test_bit(NOHZ_BALANCE_KICK, nohz_flags(cpu));
> + return test_and_clear_bit(NOHZ_BALANCE_KICK, nohz_flags(cpu));
> }
>
> #else /* CONFIG_NO_HZ_COMMON */
>
> -static inline bool got_nohz_idle_kick(void)
> +static inline bool got_nohz_idle_kick(int cpu)
> {
> return false;
> }
> @@ -1393,8 +1392,12 @@ static void sched_ttwu_pending(void)
>
> void scheduler_ipi(void)
> {
> - if (llist_empty(&this_rq()->wake_list) && !got_nohz_idle_kick()
> - && !tick_nohz_full_cpu(smp_processor_id()))
> + int cpu = smp_processor_id();
> + bool idle_kick = got_nohz_idle_kick(cpu);
This puts an unconditional atomic instruction in the IPI path.
if (test) clear();
is lots cheaper, esp. since most IPIs won't have this flag set.
> +
> + if (!(idle_kick && idle_cpu(cpu))
> + && llist_empty(&this_rq()->wake_list)
> + && !tick_nohz_full_cpu(cpu)
What's with this weird operator first split style?
> return;
>
> /*
> +enum idle_balance_type {
> + IDLE_BALANCE = 1,
> + IDLE_NOHZ_BALANCE = 2,
> +};
You might want to update the rq->idle_balance assignment in
scheduler_tick() to make sure it uses the right value (it does now, but
there's nothing stopping people from changing the values).
next prev parent reply other threads:[~2013-06-04 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 15:23 [PATCH] sched: fix clear NOHZ_BALANCE_KICK Vincent Guittot
2013-06-03 22:48 ` Frederic Weisbecker
2013-06-04 8:21 ` Vincent Guittot
2013-06-04 9:36 ` Peter Zijlstra
2013-06-04 10:26 ` Frederic Weisbecker
2013-06-04 11:11 ` Vincent Guittot
2013-06-04 11:19 ` Frederic Weisbecker
2013-06-04 11:48 ` Vincent Guittot
2013-06-04 14:44 ` Frederic Weisbecker
2013-06-04 15:29 ` Vincent Guittot
2013-06-05 13:31 ` Frederic Weisbecker
2013-06-04 11:15 ` Peter Zijlstra [this message]
2013-06-04 11:53 ` Frederic Weisbecker
2013-06-04 9:56 ` Frederic Weisbecker
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=20130604111510.GO8923@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=vincent.guittot@linaro.org \
/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