From: Patrick Bellasi <patrick.bellasi@arm.com>
To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Paul Turner <pjt@google.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
John Stultz <john.stultz@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Juri Lelli <juri.lelli@arm.com>,
Tim Murray <timmurray@google.com>, Todd Kjos <tkjos@android.com>,
Andres Oportus <andresoportus@google.com>,
Joel Fernandes <joelaf@google.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [RFCv4 6/6] cpufreq: schedutil: add util clamp for RT/DL tasks
Date: Thu, 24 Aug 2017 19:08:57 +0100 [thread overview]
Message-ID: <20170824180857.32103-7-patrick.bellasi@arm.com> (raw)
In-Reply-To: <20170824180857.32103-1-patrick.bellasi@arm.com>
Currently schedutil enforces a maximum frequency when RT/DL tasks are
RUNNABLE. Such a mandatory policy can be made more tunable from
userspace thus allowing for example to define a max frequency which is
still reasonable for the execution of a specific RT/DL workload. This
will contribute to make the RT class more friendly for power/energy
sensitive use-cases.
This patch extends the usage of util_{min,max} to the RT/DL classes.
Whenever a task in these classes is RUNNABLE, the util required is
defined by the constraints of the CPU control group the task belongs to.
Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Cc: linux-kernel@vger.kernel.org
Cc: linux-pm@vger.kernel.org
---
kernel/sched/cpufreq_schedutil.c | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
index f67c26bbade4..feca60c107bc 100644
--- a/kernel/sched/cpufreq_schedutil.c
+++ b/kernel/sched/cpufreq_schedutil.c
@@ -227,7 +227,10 @@ static void sugov_update_single(struct update_util_data *hook, u64 time,
busy = sugov_cpu_is_busy(sg_cpu);
if (flags & SCHED_CPUFREQ_RT_DL) {
- next_f = policy->cpuinfo.max_freq;
+ util = uclamp_util(smp_processor_id(), SCHED_CAPACITY_SCALE);
+ next_f = (uclamp_enabled && util < SCHED_CAPACITY_SCALE)
+ ? get_next_freq(sg_policy, util, policy->cpuinfo.max_freq)
+ : policy->cpuinfo.max_freq;
} else {
sugov_get_util(&util, &max);
sugov_iowait_boost(sg_cpu, &util, &max);
@@ -276,10 +279,15 @@ static unsigned int sugov_next_freq_shared(struct sugov_cpu *sg_cpu, u64 time)
j_sg_cpu->iowait_boost = 0;
continue;
}
- if (j_sg_cpu->flags & SCHED_CPUFREQ_RT_DL)
- return policy->cpuinfo.max_freq;
- j_util = j_sg_cpu->util;
+ if (j_sg_cpu->flags & SCHED_CPUFREQ_RT_DL) {
+ if (!uclamp_enabled)
+ return policy->cpuinfo.max_freq;
+ j_util = uclamp_util(j, SCHED_CAPACITY_SCALE);
+ } else {
+ j_util = j_sg_cpu->util;
+ }
+
j_max = j_sg_cpu->max;
if (j_util * max > j_max * util) {
util = j_util;
--
2.14.1
prev parent reply other threads:[~2017-08-24 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 18:08 [RFCv4 0/6] Add utilization clamping to the CPU controller Patrick Bellasi
2017-08-24 18:08 ` [RFCv4 1/6] sched/core: add utilization clamping to " Patrick Bellasi
2017-08-28 18:23 ` Tejun Heo
2017-09-04 17:25 ` Patrick Bellasi
2017-08-24 18:08 ` [RFCv4 2/6] sched/core: map cpu's task groups to clamp groups Patrick Bellasi
2017-08-24 18:08 ` [RFCv4 3/6] sched/core: reference count active tasks's " Patrick Bellasi
2017-08-24 18:08 ` [RFCv4 4/6] sched/core: sync task_group's with CPU's " Patrick Bellasi
2017-08-24 18:08 ` [RFCv4 5/6] cpufreq: schedutil: add util clamp for FAIR tasks Patrick Bellasi
2017-08-24 18:08 ` Patrick Bellasi [this message]
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=20170824180857.32103-7-patrick.bellasi@arm.com \
--to=patrick.bellasi@arm.com \
--cc=andresoportus@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=john.stultz@linaro.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=timmurray@google.com \
--cc=tj@kernel.org \
--cc=tkjos@android.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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
Powered by JetHome