From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Amit Kucheria <amit.kucheria@linaro.org>,
Ingo Molnar <mingo@elte.hu>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] sched: idle: Add sched balance option
Date: Mon, 28 Apr 2014 12:09:20 +0200 [thread overview]
Message-ID: <535E28D0.7050502@linaro.org> (raw)
In-Reply-To: <20140425184327.GH26782@laptop.programming.kicks-ass.net>
On 04/25/2014 08:43 PM, Peter Zijlstra wrote:
> On Fri, Apr 25, 2014 at 07:01:23PM +0200, Daniel Lezcano wrote:
>> As the sysctl is some kind of ABI, I would like to make sure we reach a
>> consensus and discuss a bit about that.
>
> We could make it a sysfs file, like /sys/power/state, which when read
> provides the words it takes.
>
> That is more flexible than a numeric sysctl for which we have to keep an
> enumeration.
I agree a numerical value is not flexible. But it sounds weird to put a
scheduler option in the sysfs and maybe more options will follow.
I am wondering if we shouldn't create a new cgroup for 'energy' and put
everything in there. So we will have more flexibility for extension and
we will be able to create a group of tasks for performance and a group
of tasks for energy saving.
Does it make sense ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2014-04-28 10:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 12:24 [PATCH 0/3] sched: idle: Provide the basis to integrate cpuidle Daniel Lezcano
2014-04-24 12:24 ` [PATCH 1/3] sched: idle: Encapsulate the code to compile it out Daniel Lezcano
2014-04-30 17:39 ` Nicolas Pitre
2014-04-24 12:24 ` [PATCH 2/3] sched: idle: Add sched balance option Daniel Lezcano
[not found] ` <CAP245DX9wewQFhcyGj5ZuNE7hHC4fRn90POC32HLF6ugja6nJg@mail.gmail.com>
2014-04-24 13:30 ` Daniel Lezcano
2014-04-25 10:54 ` Amit Kucheria
2014-04-25 11:46 ` Rafael J. Wysocki
2014-04-25 12:17 ` Daniel Lezcano
2014-04-25 13:20 ` Peter Zijlstra
2014-04-25 17:01 ` Daniel Lezcano
2014-04-25 18:43 ` Peter Zijlstra
2014-04-28 10:09 ` Daniel Lezcano [this message]
2014-04-28 10:28 ` Peter Zijlstra
2014-04-28 11:07 ` Daniel Lezcano
2014-04-28 11:21 ` Peter Zijlstra
2014-04-28 23:11 ` Rafael J. Wysocki
2014-04-29 10:00 ` Morten Rasmussen
2014-04-29 22:19 ` Rafael J. Wysocki
2014-04-29 10:25 ` Daniel Lezcano
2014-05-05 0:32 ` Rafael J. Wysocki
2014-04-29 9:26 ` Morten Rasmussen
2014-04-26 0:18 ` Rafael J. Wysocki
2014-04-26 6:17 ` Ingo Molnar
2014-04-27 13:23 ` Rafael J. Wysocki
2014-04-29 10:50 ` Morten Rasmussen
2014-04-29 22:02 ` Rafael J. Wysocki
2014-04-26 10:55 ` Peter Zijlstra
2014-04-27 13:54 ` Rafael J. Wysocki
2014-04-27 19:39 ` Peter Zijlstra
2014-04-25 13:22 ` Peter Zijlstra
2014-04-24 12:24 ` [PATCH 3/3] sched: idle: Store the idle state the cpu is Daniel Lezcano
2014-04-24 16:16 ` Rafael J. Wysocki
2014-04-24 16:13 ` [PATCH 0/3] sched: idle: Provide the basis to integrate cpuidle Rafael J. Wysocki
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=535E28D0.7050502@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
/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).