From: Vincent Guittot <vincent.guittot@linaro.org>
To: peterz@infradead.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Cc: rjw@rjwysocki.net, juri.lelli@arm.com, dietmar.eggemann@arm.com,
Morten.Rasmussen@arm.com,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH 0/2] track rt rq utilization
Date: Wed, 24 May 2017 11:00:50 +0200 [thread overview]
Message-ID: <1495616452-7582-1-git-send-email-vincent.guittot@linaro.org> (raw)
When both cfs and rt tasks compete to run on a CPU, we can see some frequency
drops with schedutil governor. In such case, the cfs_rq's utilization doesn't
reflect anymore the utilization of cfs tasks but only the remaining part that
is not used by rt tasks. We should monitor the stolen utilization and take
it into account when selecting OPP.
Patch 1 tracks utilization of rt_rq.
Patch 2 adds the rt_rq's utilization when selection OPP for cfs tasks
This patchset doesn't change the OPP selection policy for RT tasks
Vincent Guittot (2):
sched/rt: add utilization tracking
cpufreq/schedutil: add rt utilization tracking
kernel/sched/cpufreq_schedutil.c | 2 +-
kernel/sched/fair.c | 21 +++++++++++++++++++++
kernel/sched/rt.c | 9 +++++++++
kernel/sched/sched.h | 3 +++
4 files changed, 34 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2017-05-24 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 9:00 Vincent Guittot [this message]
2017-05-24 9:00 ` [RFC PATCH 1/2] sched/rt: add utilization tracking Vincent Guittot
2017-05-30 15:50 ` Morten Rasmussen
2017-05-30 16:24 ` Vincent Guittot
2017-05-31 7:57 ` Morten Rasmussen
2017-05-31 9:40 ` Peter Zijlstra
2017-05-31 10:30 ` Peter Zijlstra
2017-05-31 10:41 ` Juri Lelli
2017-05-31 11:39 ` Peter Zijlstra
2017-05-31 11:24 ` Vincent Guittot
2017-05-24 9:00 ` [PATCH 2/2] cpufreq/schedutil: add rt " 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=1495616452-7582-1-git-send-email-vincent.guittot@linaro.org \
--to=vincent.guittot@linaro.org \
--cc=Morten.Rasmussen@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
/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®