From: Nicolas Pitre <nicolas.pitre@linaro.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>
Subject: Re: [PATCH v2 0/6] sched: expel confusing usage of the term "power"
Date: Tue, 27 May 2014 10:46:01 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1405271036040.17310@knanqh.ubzr> (raw)
In-Reply-To: <CAKfTPtAb45b0KC==k7+DB_JZrXsSHcLFrn=oenX3wnS42eK6Xg@mail.gmail.com>
On Tue, 27 May 2014, Vincent Guittot wrote:
> Hi Nicolas,
>
> There are still some use of "power" instead of "capacity" in the sched
> directory like SD_SHARE_CPUPOWER, ARCH_POWER or NONTASK_POWER. They
> should also be renamed in capacity as there are also used for capacity
I thought the first one was used to identify CPU sharing the same
(electric) power domain. Or maybe I confused it with
SD_SHARE_POWERDOMAIN, illustrating the point once again for this series.
I'll create additional patches.
Nicolas
next prev parent reply other threads:[~2014-05-27 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 22:19 [PATCH v2 0/6] sched: expel confusing usage of the term "power" Nicolas Pitre
2014-05-26 22:19 ` [PATCH v2 1/6] sched/fair.c: remove "power" from struct numa_stats Nicolas Pitre
2014-05-27 3:07 ` Mike Galbraith
2014-05-27 3:18 ` Nicolas Pitre
2014-05-27 4:32 ` Mike Galbraith
2014-05-26 22:19 ` [PATCH v2 2/6] sched/fair.c: change "has_capacity" to "has_free_capacity" Nicolas Pitre
2014-05-26 22:19 ` [PATCH v2 3/6] sched/fair.c: disambiguate existing/remaining "capacity" usage Nicolas Pitre
2014-05-26 22:19 ` [PATCH v2 4/6] sched: let struct sched_group_power care about CPU capacity Nicolas Pitre
2014-05-26 22:19 ` [PATCH v2 5/6] sched: remove remaining dubious usage of "power" Nicolas Pitre
2014-05-26 22:19 ` [PATCH v2 6/6] sched: final power vs capacity cleanup Nicolas Pitre
2014-05-27 7:30 ` [PATCH v2 0/6] sched: expel confusing usage of the term "power" Vincent Guittot
2014-05-27 14:46 ` Nicolas Pitre [this message]
2014-05-27 14:07 ` Daniel Lezcano
2014-05-27 16:02 ` Nicolas Pitre
2014-05-27 16:14 ` Daniel Lezcano
2014-05-27 17:50 ` [PATCH v2 7/6] sched: rename capacity related flags Nicolas Pitre
2014-05-28 6:46 ` [PATCH v2 0/6] sched: expel confusing usage of the term "power" Peter Zijlstra
2014-06-05 10:09 ` Ingo Molnar
2014-06-05 10:16 ` Ingo Molnar
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=alpine.LFD.2.11.1405271036040.17310@knanqh.ubzr \
--to=nicolas.pitre@linaro.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=peterz@infradead.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.