From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
preeti@linux.vnet.ibm.com, Morten.Rasmussen@arm.com,
kamalesh@linux.vnet.ibm.com, riel@redhat.com, efault@gmx.de,
nicolas.pitre@linaro.org, dietmar.eggemann@arm.com,
linaro-kernel@lists.linaro.org, Paul Turner <pjt@google.com>,
Ben Segall <bsegall@google.com>
Subject: Re: [PATCH RESEND v9 04/10] sched: Make sched entity usage tracking scale-invariant
Date: Thu, 19 Feb 2015 17:34:42 +0100 [thread overview]
Message-ID: <20150219163442.GK5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1421316570-23097-5-git-send-email-vincent.guittot@linaro.org>
On Thu, Jan 15, 2015 at 11:09:24AM +0100, Vincent Guittot wrote:
> From: Morten Rasmussen <morten.rasmussen@arm.com>
>
> Apply frequency scale-invariance correction factor to usage tracking.
> Each segment of the running_load_avg geometric series is now scaled by the
> current frequency so the utilization_avg_contrib of each entity will be
> invariant with frequency scaling.
> As a result, utilization_load_avg which is
> the sum of utilization_avg_contrib, becomes invariant too. So the usage level
> that is returned by get_cpu_usage, stays relative to the max frequency as the
> cpu_capacity which is is compared against.
> Then, we want the keep the load tracking values in a 32bits type, which implies
> that the max value of {runnable|running}_avg_sum must be lower than
> 2^32/88761=48388 (88761 is the max weigth of a task).
> As LOAD_AVG_MAX = 47742,
> arch_scale_freq_capacity must return a value less than
> (48388/47742) << SCHED_CAPACITY_SHIFT = 1037 (SCHED_SCALE_CAPACITY = 1024).
> So we define the range to [0..SCHED_SCALE_CAPACITY] in order to avoid overflow.
> cc: Paul Turner <pjt@google.com>
> cc: Ben Segall <bsegall@google.com>
>
> Signed-off-by: Morten Rasmussen <morten.rasmussen@arm.com>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
> kernel/sched/fair.c | 21 ++++++++++++++-------
> 1 file changed, 14 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index a96affd..a5039da 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -2266,6 +2266,8 @@ static u32 __compute_runnable_contrib(u64 n)
> return contrib + runnable_avg_yN_sum[n];
> }
>
> +unsigned long __weak arch_scale_freq_capacity(struct sched_domain *sd, int cpu);
There is no actual function definition in this patch; this would hinder
linking, no?
> if (running)
> + sa->running_avg_sum += delta_w * scale_freq
> + >> SCHED_CAPACITY_SHIFT;
> if (running)
> + sa->running_avg_sum += runnable_contrib * scale_freq
> + >> SCHED_CAPACITY_SHIFT;
> if (running)
> + sa->running_avg_sum += delta * scale_freq
> + >> SCHED_CAPACITY_SHIFT;
If you're going to respin; please but {} around that.
next prev parent reply other threads:[~2015-02-19 16:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 10:09 [PATCH RESEND v9 00/10] sched: consolidation of CPU capacity and usage Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 01/10] sched: add utilization_avg_contrib Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 02/10] sched: Track group sched_entity usage contributions Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 03/10] sched: remove frequency scaling from cpu_capacity Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 04/10] sched: Make sched entity usage tracking scale-invariant Vincent Guittot
2015-02-19 16:34 ` Peter Zijlstra [this message]
2015-02-19 17:02 ` Morten Rasmussen
2015-02-19 17:05 ` Peter Zijlstra
2015-02-20 9:21 ` Morten Rasmussen
2015-01-15 10:09 ` [PATCH RESEND v9 05/10] sched: make scale_rt invariant with frequency Vincent Guittot
2015-02-19 16:52 ` Peter Zijlstra
2015-02-19 17:18 ` Morten Rasmussen
2015-02-24 10:21 ` Vincent Guittot
2015-02-24 11:33 ` Dietmar Eggemann
2015-01-15 10:09 ` [PATCH RESEND v9 06/10] sched: add per rq cpu_capacity_orig Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 07/10] sched: get CPU's usage statistic Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 08/10] sched: replace capacity_factor by usage Vincent Guittot
2015-02-20 11:14 ` Peter Zijlstra
2015-02-20 13:31 ` Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 09/10] sched: add SD_PREFER_SIBLING for SMT level Vincent Guittot
2015-01-15 10:09 ` [PATCH RESEND v9 10/10] sched: move cfs task on a CPU with higher capacity Vincent Guittot
2015-02-20 11:27 ` Peter Zijlstra
2015-02-20 13:54 ` Vincent Guittot
2015-02-20 16:26 ` Peter Zijlstra
2015-02-19 12:49 ` [PATCH RESEND v9 00/10] sched: consolidation of CPU capacity and usage Morten Rasmussen
2015-02-20 11:34 ` Peter Zijlstra
2015-02-20 11:52 ` Morten Rasmussen
2015-02-20 14:13 ` Vincent Guittot
2015-02-20 14:35 ` Morten Rasmussen
2015-02-20 14:54 ` Vincent Guittot
2015-02-23 15:45 ` Morten Rasmussen
2015-02-24 10:38 ` Vincent Guittot
2015-02-24 11:29 ` Morten Rasmussen
2015-02-24 12:18 ` 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=20150219163442.GK5029@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Morten.Rasmussen@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=pjt@google.com \
--cc=preeti@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--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