From: vincent.guittot@linaro.org (Vincent Guittot)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 10/10] sched: make scale_rt invariant with frequency
Date: Mon, 3 Nov 2014 17:14:15 +0100 [thread overview]
Message-ID: <CAKfTPtBQmhv1Lpjsak27m+GW=3tBuskRqv5UiL_cW7rGnVBp9g@mail.gmail.com> (raw)
In-Reply-To: <20141103155129.GK12706@worktop.programming.kicks-ass.net>
On 3 November 2014 16:51, Peter Zijlstra <peterz@infradead.org> wrote:
> On Fri, Oct 31, 2014 at 09:47:32AM +0100, Vincent Guittot wrote:
>> 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 ?
>
> Well, you put it in quite a hot path on the CFS side too, so it had
> better be blazing fast anyhow.
>
>
> That said, can you move all the running + invariance bits at the
> beginning of the patch set, these appear to be the least controversial
> bits and 'desired' by quite a few people, so we'll try and get those
> agreed upon and merged first.
ok
I'm going to resend with the following order
sched: add utilization_avg_contrib
sched: Track group sched_entity usage contributions
sched: remove frequency scaling from cpu_capacity
sched: Make sched entity usage tracking scale-invariant
sched: make scale_rt invariant with frequency
sched: add per rq cpu_capacity_orig
sched: get CPU's usage statistic
sched: replace capacity_factor by usage
sched: add SD_PREFER_SIBLING for SMT level
sched: move cfs task on a CPU with higher capacity
next prev parent reply other threads:[~2014-11-03 16:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 8:47 [PATCH v8 00/10] sched: consolidation of CPU capacity and usage Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 01/10] sched: add per rq cpu_capacity_orig Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 02/10] sched: remove frequency scaling from cpu_capacity Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 03/10] sched: move cfs task on a CPU with higher capacity Vincent Guittot
2014-11-04 8:30 ` Wanpeng Li
2014-11-04 9:41 ` Vincent Guittot
2014-11-04 10:42 ` Wanpeng Li
2014-11-04 11:10 ` Vincent Guittot
2014-11-18 10:47 ` Wanpeng Li
2014-11-18 11:00 ` Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 04/10] sched: add utilization_avg_contrib Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 05/10] sched: Track group sched_entity usage contributions Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 06/10] sched: get CPU's usage statistic Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 07/10] sched: replace capacity_factor by usage Vincent Guittot
2014-11-03 7:01 ` Wanpeng Li
2014-11-03 10:59 ` Vincent Guittot
2014-11-03 15:29 ` Peter Zijlstra
2014-10-31 8:47 ` [PATCH v8 08/10] sched: add SD_PREFER_SIBLING for SMT level Vincent Guittot
2014-11-04 3:21 ` Wanpeng Li
2014-11-04 8:58 ` Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 09/10] sched: Make sched entity usage tracking scale-invariant Vincent Guittot
2014-10-31 8:47 ` [PATCH v8 10/10] sched: make scale_rt invariant with frequency Vincent Guittot
2014-11-03 15:51 ` Peter Zijlstra
2014-11-03 16:14 ` Vincent Guittot [this message]
2014-11-03 2:12 ` [PATCH v8 00/10] sched: consolidation of CPU capacity and usage Wanpeng Li
2014-11-03 10:55 ` Vincent Guittot
2014-11-03 13:03 ` Wanpeng Li
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='CAKfTPtBQmhv1Lpjsak27m+GW=3tBuskRqv5UiL_cW7rGnVBp9g@mail.gmail.com' \
--to=vincent.guittot@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).