From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
patches@linaro.org, Ingo Molnar <mingo@elte.hu>,
Paul Turner <pjt@google.com>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [RFC] sched: Ensure cpu_power periodic update
Date: Thu, 15 Dec 2011 11:08:30 +0100 [thread overview]
Message-ID: <1323943710.18942.24.camel@twins> (raw)
In-Reply-To: <1323717668-2143-1-git-send-email-vincent.guittot@linaro.org>
On Mon, 2011-12-12 at 20:21 +0100, Vincent Guittot wrote:
> With a lot of small tasks, the softirq sched is nearly never called
> when no_hz is enable. In this case the load_balance is mainly called with
> the newly_idle mode which doesn't update the cpu_power.
> Add a next_update field which ensure a maximum update period when
> there is short activity
> + if (local_group) {
> + if (idle != CPU_NEWLY_IDLE) {
> + if (balance_cpu != this_cpu) {
> + *balance = 0;
> + return;
> + }
> + update_group_power(sd, this_cpu);
> + } else if (time_after_eq(jiffies, group->sgp->next_update))
> + update_group_power(sd, this_cpu);
> }
Hmm, I would have expected it to be called from the NOHZ balancing path
instead of the new_idle path. Your changelog fails to mentions any
considerations on this..
Then again, its probably easier to keep update_group_power on this_cpu
than to allow a remote update of your cpu_power.
So I'm not opposed to this patch, I'd just like a little extra
clarification.
next prev parent reply other threads:[~2011-12-15 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 19:21 Vincent Guittot
2011-12-15 10:08 ` Peter Zijlstra [this message]
2011-12-15 13:36 ` Vincent Guittot
2011-12-16 0:58 ` Suresh Siddha
2011-12-16 8:23 ` Vincent Guittot
2012-01-04 8:22 ` Vincent Guittot
2012-01-06 12:10 ` Peter Zijlstra
2012-01-28 12:07 ` [tip:sched/core] " tip-bot for Vincent Guittot
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=1323943710.18942.24.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=patches@linaro.org \
--cc=pjt@google.com \
--cc=suresh.b.siddha@intel.com \
--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
all inboxes | Powered by JetHome®