From: Patrick Bellasi <patrick.bellasi@arm.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Chris Redpath <Chris.Redpath@arm.com>,
Joel Fernandes <joelaf@google.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH 2/2] cpufreq: schedutil: consolidate capacity margin calculation
Date: Mon, 25 Sep 2017 14:55:07 +0100 [thread overview]
Message-ID: <20170925135507.GA3621@e110439-lin> (raw)
In-Reply-To: <1506121484-8260-2-git-send-email-leo.yan@linaro.org>
On 23-Sep 07:04, Leo Yan wrote:
> Scheduler CFS class has variable 'capacity_margin' to calculate the
> capacity margin, and schedutil governor also needs to compensate the
> same margin for frequency tipping point. Below are formulas used in
> CFS class and schedutil governor separately:
>
> CFS: U` = U * capacity_margin / 1024 = U * 1.25
> Schedutil: U` = U + U >> 2 = U + U * 0.25 = U * 1.25
>
> This patch consolidates the capacity margin calculation so let
> schedutil to use same formula with CFS class. As result this can avoid
> the mismatch issue between schedutil and CFS class after change
> 'capacity_margin' to other values.
>
> Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
> Cc: Morten Rasmussen <morten.rasmussen@arm.com>
> Cc: Chris Redpath <Chris.Redpath@arm.com>
> Cc: Joel Fernandes <joelaf@google.com>
> Cc: Vincent Guittot <vincent.guittot@linaro.org>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
> kernel/sched/cpufreq_schedutil.c | 5 +++--
> kernel/sched/sched.h | 1 +
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> index 9209d83..067abbe 100644
> --- a/kernel/sched/cpufreq_schedutil.c
> +++ b/kernel/sched/cpufreq_schedutil.c
> @@ -155,7 +155,8 @@ static void sugov_update_commit(struct sugov_policy *sg_policy, u64 time,
> *
> * next_freq = C * curr_freq * util_raw / max
> *
> - * Take C = 1.25 for the frequency tipping point at (util / max) = 0.8.
> + * Take C = capacity_margin / 1024 = 1.25, so it's for the frequency tipping
> + * point at (util / max) = 0.8.
> *
> * The lowest driver-supported frequency which is equal or greater than the raw
> * next_freq (as calculated above) is returned, subject to policy min/max and
> @@ -168,7 +169,7 @@ static unsigned int get_next_freq(struct sugov_policy *sg_policy,
> unsigned int freq = arch_scale_freq_invariant() ?
> policy->cpuinfo.max_freq : policy->cur;
>
> - freq = (freq + (freq >> 2)) * util / max;
> + freq = (freq * capacity_margin / 1024) * util / max;
The compiler should be smart enough but perhaps you can better use:
freq *= (capacity_margin >> SCHED_CAPACITY_SHIFT));
freq *= util / max;
> if (freq == sg_policy->cached_raw_freq && sg_policy->next_freq != UINT_MAX)
> return sg_policy->next_freq;
> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> index 14db76c..cf75bdc 100644
> --- a/kernel/sched/sched.h
> +++ b/kernel/sched/sched.h
> @@ -52,6 +52,7 @@ struct cpuidle_state;
> #define TASK_ON_RQ_MIGRATING 2
>
> extern __read_mostly int scheduler_running;
> +extern unsigned int capacity_margin __read_mostly;
>
> extern unsigned long calc_load_update;
> extern atomic_long_t calc_load_tasks;
> --
> 2.7.4
>
--
#include <best/regards.h>
Patrick Bellasi
next prev parent reply other threads:[~2017-09-25 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 23:04 [PATCH 1/2] sched/fair: make capacity_margin __read_mostly Leo Yan
2017-09-22 23:04 ` [PATCH 2/2] cpufreq: schedutil: consolidate capacity margin calculation Leo Yan
2017-09-25 8:15 ` Peter Zijlstra
2017-09-25 13:55 ` Patrick Bellasi [this message]
2017-09-28 6:33 ` Leo Yan
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=20170925135507.GA3621@e110439-lin \
--to=patrick.bellasi@arm.com \
--cc=Chris.Redpath@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelaf@google.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.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