From: Peter Zijlstra <peterz@infradead.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 6/6] sched: final power vs capacity cleanup
Date: Thu, 15 May 2014 09:29:29 +0200 [thread overview]
Message-ID: <20140515072929.GZ30445@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1400101030-17717-7-git-send-email-nicolas.pitre@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
On Wed, May 14, 2014 at 04:57:10PM -0400, Nicolas Pitre wrote:
> It is better not to think about compute capacity as being equivalent to
> "CPU power". The upcoming "power aware" scheduler may create confusion
> with the notion of energy consumption if "power" is used too liberally.
>
> This contains the architecture visible changes. Incidentally, only ARM
> takes advantage of the available pow^H^H^Hcapacity scaling hooks and
> therefore those changes outside kernel/sched/ are confined to one ARM
> specific file. The default arch_scale_smt_power() hook is not overridden
> by anyone.
>
> Replacements are as follows:
>
> arch_scale_freq_power --> arch_scale_freq_capacity
> arch_scale_smt_power --> arch_scale_smt_capacity
> SCHED_POWER_SCALE --> SCHED_CAPA_SCALE
> SCHED_POWER_SHIFT --> SCHED_POWER_SHIFT
The patch seems to actually make that CAPA_SHIFT
> The local usage of "power" in arch/arm/kernel/topology.c is also changed
> to "capacity" as appropriate.
For some reason every time I read: 'capa' I think of some south American
monster -- http://en.wikipedia.org/wiki/Chupacabra, I'm not at all sure
why my brain links them.
But yes, once we kill the capacity stuff we have now with some
utilization bound, capacity becomes uniquely the compute capacity.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-15 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 20:57 [PATCH 0/6] sched: expel confusing usage of the term "power" Nicolas Pitre
2014-05-14 20:57 ` [PATCH 1/6] sched/fair.c: remove "power" from struct numa_stats Nicolas Pitre
2014-05-14 20:57 ` [PATCH 2/6] sched/fair.c: change "has_capacity" to "has_free_capacity" Nicolas Pitre
2014-05-15 7:21 ` Peter Zijlstra
2014-05-15 7:28 ` Vincent Guittot
2014-05-14 20:57 ` [PATCH 3/6] sched/fair.c: disambiguate existing/remaining "capacity" usage Nicolas Pitre
2014-05-15 7:39 ` Vincent Guittot
2014-05-15 16:06 ` Nicolas Pitre
2014-05-14 20:57 ` [PATCH 4/6] sched: let struct sched_group_power care about CPU capacity Nicolas Pitre
2014-05-14 20:57 ` [PATCH 5/6] sched: remove remaining power to the CPU Nicolas Pitre
2014-05-16 9:00 ` Preeti Murthy
2014-05-16 16:34 ` Nicolas Pitre
2014-05-14 20:57 ` [PATCH 6/6] sched: final power vs capacity cleanup Nicolas Pitre
2014-05-15 7:29 ` Peter Zijlstra [this message]
2014-05-15 16:12 ` Nicolas Pitre
2014-05-20 3:05 ` Nicolas Pitre
2014-05-15 7:41 ` [PATCH 0/6] sched: expel confusing usage of the term "power" Vincent Guittot
2014-05-15 16:15 ` Nicolas Pitre
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=20140515072929.GZ30445@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.lezcano@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@rjwysocki.net \
--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.