From: Steve Muckle <steve.muckle@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: 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>,
Steve Muckle <smuckle@linaro.org>
Subject: [PATCH 0/2] utilization changes for schedutil
Date: Fri, 26 Aug 2016 11:40:46 -0700 [thread overview]
Message-ID: <1472236848-17038-1-git-send-email-smuckle@linaro.org> (raw)
The first patch (which is a re-send) corrects an issue with utilization on SMT
platforms. Currently CFS utilization is being roughly doubled on these
platforms due to differences in the way PELT and overall max CPU capacity are
calculated.
The second patch moves away from the policy of going to fmax during RT task
activity, instead using rt_avg as an estimate of RT utilization.
Steve Muckle (2):
sched: cpufreq: ignore SMT when determining max cpu capacity
sched: cpufreq: use rt_avg as estimate of required RT CPU capacity
kernel/sched/cpufreq_schedutil.c | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
--
2.7.3
next reply other threads:[~2016-08-26 18:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 18:40 Steve Muckle [this message]
2016-08-26 18:40 ` [PATCH 1/2] sched: cpufreq: ignore SMT when determining max cpu capacity Steve Muckle
2016-08-31 1:27 ` Rafael J. Wysocki
2016-08-31 14:34 ` Peter Zijlstra
2016-09-12 22:25 ` Rafael J. Wysocki
2016-08-26 18:40 ` [PATCH 2/2] sched: cpufreq: use rt_avg as estimate of required RT CPU capacity Steve Muckle
2016-08-31 1:31 ` Rafael J. Wysocki
2016-08-31 14:49 ` Steve Muckle
2016-08-31 14:39 ` Peter Zijlstra
2016-08-31 15:08 ` Steve Muckle
2016-08-31 16:28 ` Thomas Gleixner
2016-08-31 16:40 ` Peter Zijlstra
2016-08-31 17:00 ` Juri Lelli
2016-09-01 7:12 ` Peter Zijlstra
2016-09-01 21:48 ` Steve Muckle
2016-09-02 9:35 ` Juri Lelli
2016-09-02 12:17 ` Thomas Gleixner
2016-08-31 22:50 ` Rafael J. Wysocki
2016-09-02 8:12 ` Thomas Gleixner
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=1472236848-17038-1-git-send-email-smuckle@linaro.org \
--to=steve.muckle@linaro.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=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=smuckle@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).