From: Ingo Molnar <mingo@kernel.org>
To: Steve Muckle <steve.muckle@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Juri Lelli <Juri.Lelli@arm.com>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Ricky Liang <jcliang@chromium.org>
Subject: Re: [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection
Date: Thu, 3 Mar 2016 15:21:07 +0100 [thread overview]
Message-ID: <20160303142107.GA10948@gmail.com> (raw)
In-Reply-To: <1456190570-4475-4-git-send-email-smuckle@linaro.org>
* Steve Muckle <steve.muckle@linaro.org> wrote:
> From: Michael Turquette <mturquette@baylibre.com>
>
> Scheduler-driven CPU frequency selection hopes to exploit both
> per-task and global information in the scheduler to improve frequency
> selection policy, achieving lower power consumption, improved
> responsiveness/performance, and less reliance on heuristics and
> tunables. For further discussion on the motivation of this integration
> see [0].
>
> This patch implements a shim layer between the Linux scheduler and the
> cpufreq subsystem. The interface accepts capacity requests from the
> CFS, RT and deadline sched classes. The requests from each sched class
> are summed on each CPU with a margin applied to the CFS and RT
> capacity requests to provide some headroom. Deadline requests are
> expected to be precise enough given their nature to not require
> headroom. The maximum total capacity request for a CPU in a frequency
> domain drives the requested frequency for that domain.
>
> Policy is determined by both the sched classes and this shim layer.
>
> Note that this algorithm is event-driven. There is no polling loop to
> check cpu idle time nor any other method which is unsynchronized with
> the scheduler, aside from an optional throttling mechanism.
>
> Thanks to Juri Lelli <juri.lelli@arm.com> for contributing design ideas,
> code and test results, and to Ricky Liang <jcliang@chromium.org>
> for initialization and static key inc/dec fixes.
>
> [0] http://article.gmane.org/gmane.linux.kernel/1499836
>
> [smuckle@linaro.org: various additions and fixes, revised commit text]
>
> CC: Ricky Liang <jcliang@chromium.org>
> Signed-off-by: Michael Turquette <mturquette@baylibre.com>
> Signed-off-by: Juri Lelli <juri.lelli@arm.com>
> Signed-off-by: Steve Muckle <smuckle@linaro.org>
> ---
> drivers/cpufreq/Kconfig | 21 ++
> include/linux/cpufreq.h | 3 +
> include/linux/sched.h | 8 +
> kernel/sched/Makefile | 1 +
> kernel/sched/cpufreq_sched.c | 459 +++++++++++++++++++++++++++++++++++++++++++
Please rename this to kernel/sched/cpufreq.c - no need to say 'sched' twice! :-)
> kernel/sched/sched.h | 51 +++++
> 6 files changed, 543 insertions(+)
> create mode 100644 kernel/sched/cpufreq_sched.c
So I really like how you push all high level code into kernel/sched/cpufreq.c and
use the cpufreq drivers only for actual low level frequency switching.
It would be nice to converge this code with the code from Rafael:
[PATCH 0/6] cpufreq: schedutil governor
i.e. use scheduler internal metrics within the scheduler, and create a clear
interface between low level cpufreq drivers and the cpufreq code living in the
scheduler.
Thanks,
Ingo
next prev parent reply other threads:[~2016-03-03 14:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 1:22 [RFCv7 PATCH 00/10] sched: scheduler-driven CPU frequency selection Steve Muckle
2016-02-23 1:22 ` [RFCv7 PATCH 01/10] sched: Compute cpu capacity available at current frequency Steve Muckle
2016-02-23 1:41 ` Rafael J. Wysocki
2016-02-23 9:19 ` Peter Zijlstra
2016-02-26 1:37 ` Rafael J. Wysocki
2016-02-26 9:14 ` Peter Zijlstra
2016-02-23 1:22 ` [RFCv7 PATCH 02/10] cpufreq: introduce cpufreq_driver_is_slow Steve Muckle
2016-02-23 1:31 ` Rafael J. Wysocki
2016-02-26 0:50 ` Michael Turquette
2016-02-26 1:07 ` Steve Muckle
2016-02-26 1:16 ` Rafael J. Wysocki
[not found] ` <20160226185503.2278.20479@quark.deferred.io>
2016-02-26 21:00 ` Rafael J. Wysocki
2016-02-23 1:22 ` [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection Steve Muckle
2016-02-25 3:55 ` Rafael J. Wysocki
2016-02-25 9:21 ` Peter Zijlstra
2016-02-25 21:04 ` Rafael J. Wysocki
2016-02-25 9:28 ` Peter Zijlstra
2016-02-25 21:08 ` Rafael J. Wysocki
2016-02-26 9:18 ` Peter Zijlstra
2016-02-27 0:08 ` Rafael J. Wysocki
2016-03-01 12:57 ` Peter Zijlstra
2016-03-01 19:44 ` Rafael J. Wysocki
2016-02-25 11:04 ` Rafael J. Wysocki
2016-02-26 0:34 ` Steve Muckle
2016-02-27 2:39 ` Rafael J. Wysocki
2016-02-27 4:17 ` Steve Muckle
2016-02-28 2:26 ` Rafael J. Wysocki
2016-03-01 14:31 ` Peter Zijlstra
2016-03-01 20:32 ` Rafael J. Wysocki
2016-03-01 13:26 ` Peter Zijlstra
2016-03-01 13:17 ` Peter Zijlstra
2016-03-02 7:49 ` Michael Turquette
2016-03-03 2:49 ` Rafael J. Wysocki
2016-03-03 3:50 ` Steve Muckle
2016-03-03 9:34 ` Juri Lelli
2016-03-03 13:03 ` Peter Zijlstra
2016-03-03 14:21 ` Ingo Molnar [this message]
2016-02-23 1:22 ` [RFCv7 PATCH 04/10] sched/fair: add triggers for OPP change requests Steve Muckle
2016-03-01 6:51 ` Ricky Liang
2016-03-03 3:55 ` Steve Muckle
2016-02-23 1:22 ` [RFCv7 PATCH 05/10] sched/{core,fair}: trigger OPP change request on fork() Steve Muckle
2016-02-23 1:22 ` [RFCv7 PATCH 06/10] sched/fair: cpufreq_sched triggers for load balancing Steve Muckle
2016-02-23 1:22 ` [RFCv7 PATCH 07/10] sched/fair: jump to max OPP when crossing UP threshold Steve Muckle
2016-02-23 1:22 ` [RFCv7 PATCH 08/10] sched: remove call of sched_avg_update from sched_rt_avg_update Steve Muckle
2016-02-23 1:22 ` [RFCv7 PATCH 09/10] sched/deadline: split rt_avg in 2 distincts metrics Steve Muckle
2016-02-23 1:22 ` [RFCv7 PATCH 10/10] sched: rt scheduler sets capacity requirement Steve Muckle
2016-02-23 1:33 ` [RFCv7 PATCH 00/10] sched: scheduler-driven CPU frequency selection Steve Muckle
2016-03-30 0:45 ` Yuyang Du
2016-03-31 1:35 ` Steve Muckle
2016-03-30 20:22 ` Yuyang Du
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=20160303142107.GA10948@gmail.com \
--to=mingo@kernel.org \
--cc=Juri.Lelli@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=jcliang@chromium.org \
--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=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).