From: Alex Shi <alex.shi@intel.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: rob@landley.net, mingo@redhat.com, peterz@infradead.org,
suresh.b.siddha@intel.com, arjan@linux.intel.com,
vincent.guittot@linaro.org, tglx@linutronix.de,
gregkh@linuxfoundation.org, andre.przywara@amd.com, rjw@sisk.pl,
paul.gortmaker@windriver.com, akpm@linux-foundation.org,
paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
cl@linux.com, pjt@google.com
Subject: Re: [RFC PATCH 1/3] sched: add sched_policy and it's sysfs interface
Date: Wed, 07 Nov 2012 21:03:25 +0800 [thread overview]
Message-ID: <509A5C1D.601@intel.com> (raw)
In-Reply-To: <CAJRGBZzPcCGAz1nc_rGpVd5rq2sZiFZ0Gu_PVnsEzhkaUd7zFA@mail.gmail.com>
On 11/06/2012 11:20 PM, Luming Yu wrote:
> On Tue, Nov 6, 2012 at 8:09 AM, Alex Shi <alex.shi@intel.com> wrote:
>> This patch add the power aware scheduler knob into sysfs:
>
> The problem is user doesn't know how to use this knob.
>
> Based on what data, people could select one policy which could be surely
> better than another?
>
> "Packing small tasks" approach could be better and more intelligent.
> http://thread.gmane.org/gmane.linux.kernel/1348522
It is not conflict with this patchset. :)
>
> Just some random thoughts, as I didn't have chance to look into the
> details of that patch set yet. But to me, we need to exploit the fact
> that we could automatically bind a group of tasks on minimal set of
> CPUs that can provide sufficient CPU cycles that are comparable to
> a"cpu- run-average" that the task group can get in pure CFS situation
> in a given period, until we see more CPU is needed.Then we probably
> can maintain required CPU power available to the corresponding
> workload, while leaving all other CPUs into power saving mode. The
> problem is historical data suggested pattern could become invalid in
> future, then we need more CPUs in future..I think this is the point we
> need to know before spread or not-spread decision ...if spread would
> not help CPU-run-average ,we don't need waste CPU power..but I don't
> know how hard it could be. But I'm pretty sure sysfs knob is harder.
> :-) /l
>
--
Thanks
Alex
next prev parent reply other threads:[~2012-11-07 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 13:09 [RFC PATCH 0/3] power aware scheduling Alex Shi
2012-11-06 13:09 ` [RFC PATCH 1/3] sched: add sched_policy and it's sysfs interface Alex Shi
2012-11-06 13:48 ` Greg KH
2012-11-07 12:27 ` Alex Shi
2012-11-07 14:41 ` Greg KH
2012-11-08 14:40 ` Alex Shi
2012-11-06 15:20 ` Luming Yu
2012-11-07 13:03 ` Alex Shi [this message]
2012-11-06 13:09 ` [RFC PATCH 2/3] sched: power aware load balance, Alex Shi
2012-11-06 19:51 ` Andrew Morton
2012-11-07 12:42 ` Alex Shi
2012-11-07 4:37 ` Preeti Murthy
2012-11-07 13:27 ` Alex Shi
2012-11-11 18:49 ` Preeti Murthy
2012-11-12 3:05 ` Alex Shi
2012-11-06 13:09 ` [RFC PATCH 3/3] sched: add power aware scheduling in fork/exec/wake Alex Shi
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=509A5C1D.601@intel.com \
--to=alex.shi@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andre.przywara@amd.com \
--cc=arjan@linux.intel.com \
--cc=cl@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rjw@sisk.pl \
--cc=rob@landley.net \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox