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
Subject: Re: [PATCH RESEND v9 05/10] sched: make scale_rt invariant with frequency
Date: Thu, 19 Feb 2015 17:52:41 +0100 [thread overview]
Message-ID: <20150219165241.GL5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1421316570-23097-6-git-send-email-vincent.guittot@linaro.org>
On Thu, Jan 15, 2015 at 11:09:25AM +0100, Vincent Guittot wrote:
> The average running time of RT tasks is used to estimate the remaining compute
> capacity for CFS tasks. This remaining capacity is the original capacity scaled
> down by a factor (aka scale_rt_capacity). This estimation of available capacity
> must also be invariant with frequency scaling.
>
> A frequency scaling factor is applied on the running time of the RT tasks for
> computing scale_rt_capacity.
>
> In sched_rt_avg_update, we scale the RT execution time like below:
> rq->rt_avg += rt_delta * arch_scale_freq_capacity() >> SCHED_CAPACITY_SHIFT
>
> Then, scale_rt_capacity can be summarized by:
> scale_rt_capacity = SCHED_CAPACITY_SCALE -
> ((rq->rt_avg << SCHED_CAPACITY_SHIFT) / period)
>
> We can optimize by removing right and left shift in the computation of rq->rt_avg
> and scale_rt_capacity
So far so good..
> The call to arch_scale_frequency_capacity in the rt scheduling path might be
> a concern for RT folks because I'm not sure whether we can rely on
> arch_scale_freq_capacity to be short and efficient ?
No, that is, arch_scale_frequency_capacity() _must_ be short and
efficient, event for the fair class, its called in very hot paths.
I think we've talked about this before; this function should basically
only return a cached value, which is periodically updated through some
means.
But lets see, I've yet to see an actual implementation of it; and its
got that sd argument, curious what you're going to do with that.
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
> kernel/sched/fair.c | 17 +++++------------
> kernel/sched/sched.h | 4 +++-
> 2 files changed, 8 insertions(+), 13 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index a5039da..b37c27b 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -5801,19 +5801,12 @@ static unsigned long scale_rt_capacity(int cpu)
>
> total = sched_avg_period() + delta;
>
> - if (unlikely(total < avg)) {
> - /* Ensures that capacity won't end up being negative */
> - available = 0;
> - } else {
> - available = total - avg;
> - }
> + used = div_u64(avg, total);
>
> - if (unlikely((s64)total < SCHED_CAPACITY_SCALE))
> - total = SCHED_CAPACITY_SCALE;
> + if (likely(used < SCHED_CAPACITY_SCALE))
> + return SCHED_CAPACITY_SCALE - used;
>
> - total >>= SCHED_CAPACITY_SHIFT;
> -
> - return div_u64(available, total);
> + return 1;
> }
This makes a lot of changes not commented on in the Changelog.
I think it makes sense, but this has always been horrible.
next prev parent reply other threads:[~2015-02-19 16:52 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
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 [this message]
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=20150219165241.GL5029@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Morten.Rasmussen@arm.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.