From: Peter Zijlstra <peterz@infradead.org>
To: Steve Muckle <steve.muckle@linaro.org>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <Juri.Lelli@arm.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH 1/2] sched/fair: move cpufreq hook to update_cfs_rq_load_avg()
Date: Fri, 1 Apr 2016 11:20:19 +0200 [thread overview]
Message-ID: <20160401092019.GN3430@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <56FD95EE.6090007@linaro.org>
On Thu, Mar 31, 2016 at 02:26:06PM -0700, Steve Muckle wrote:
> > Can't, the way the wakeup path is constructed we would be sending the
> > IPI way before we know about utilization.
>
> Sorry I thought we were referring to the possibility of sending an IPI
> to just run the cpufreq driver rather than to conduct the whole wakeup
> operation.
>
> My thinking was in CFS we get rid of the (cpu == smp_processor_id())
> condition for calling the cpufreq hook.
>
> The sched governor can then calculate utilization and frequency required
> for cpu. If (cpu == smp_processor_id()), the update is processed
> normally. If (cpu != smp_processor_id()) and the new frequency is higher
> than cpu's Fcur, the sched gov IPIs cpu to continue running the update
> operation. Otherwise, the update is dropped.
>
> Does that sound plausible?
Can be done I suppose..
next prev parent reply other threads:[~2016-04-01 9:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 0:21 [PATCH 1/2] sched/fair: move cpufreq hook to update_cfs_rq_load_avg() Steve Muckle
2016-03-22 0:21 ` [PATCH 2/2] sched/fair: do not call cpufreq hook unless util changed Steve Muckle
2016-03-24 23:47 ` Sai Gurrappadi
2016-03-25 1:01 ` Steve Muckle
2016-03-25 21:24 ` Sai Gurrappadi
2016-04-23 12:57 ` [tip:sched/core] sched/fair: Do " tip-bot for Steve Muckle
2016-03-28 12:02 ` [PATCH 1/2] sched/fair: move cpufreq hook to update_cfs_rq_load_avg() Dietmar Eggemann
2016-03-28 16:34 ` Steve Muckle
2016-03-28 18:30 ` Dietmar Eggemann
2016-03-28 19:38 ` Steve Muckle
2016-03-30 19:35 ` Peter Zijlstra
2016-03-31 1:42 ` Steve Muckle
2016-03-31 7:37 ` Peter Zijlstra
2016-03-31 21:26 ` Steve Muckle
2016-04-01 9:20 ` Peter Zijlstra [this message]
2016-04-11 19:28 ` Steve Muckle
2016-04-11 21:20 ` Rafael J. Wysocki
2016-04-12 14:29 ` Rafael J. Wysocki
2016-04-12 19:38 ` Steve Muckle
2016-04-13 14:45 ` Rafael J. Wysocki
2016-04-13 17:53 ` Steve Muckle
2016-04-13 19:39 ` Rafael J. Wysocki
2016-04-13 0:08 ` Steve Muckle
2016-04-13 4:48 ` Rafael J. Wysocki
2016-04-13 16:05 ` Rafael J. Wysocki
2016-04-13 16:07 ` Rafael J. Wysocki
2016-04-13 18:06 ` Steve Muckle
2016-04-13 19:50 ` Rafael J. Wysocki
2016-04-20 2:22 ` Steve Muckle
2016-03-31 9:27 ` Vincent Guittot
2016-03-31 9:34 ` Peter Zijlstra
2016-03-31 9:50 ` Vincent Guittot
2016-03-31 10:47 ` Peter Zijlstra
2016-03-31 12:14 ` Vincent Guittot
2016-03-31 12:34 ` Peter Zijlstra
2016-03-31 12:50 ` Vincent Guittot
2016-04-23 12:57 ` [tip:sched/core] sched/fair: Move " tip-bot for Steve Muckle
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=20160401092019.GN3430@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Juri.Lelli@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=mturquette@baylibre.com \
--cc=patrick.bellasi@arm.com \
--cc=rafael@kernel.org \
--cc=steve.muckle@linaro.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