From: Alex Shi <alex.shi@linaro.org>
To: Abel Vesa <abelvesa@gmail.com>,
alex.shi@intel.com, vincent.guittot@linaro.org,
peterz@infradead.org, pjt@google.com, efault@gmx.de,
rjw@rjwysocki.net, morten.rasmussen@arm.com,
svaidy@linux.vnet.ibm.com, arjan@linux.intel.com,
mingo@kernel.org, preeti@linux.vnet.ibm.com
Cc: linaro-kernel@lists.linaro.org, corbet@lwn.net,
catalin.marinas@arm.com, markgross@thegnar.org,
sundar.iyer@intel.com, linux-kernel@vger.kernel.org,
mike.turquette@linaro.org, akpm@linux-foundation.org,
paulmck@linux.vnet.ibm.com, dietmar.eggemann@arm.com
Subject: Re: Power Scheduler Design
Date: Sun, 07 Sep 2014 07:29:33 -0700 [thread overview]
Message-ID: <540C6BCD.70504@linaro.org> (raw)
In-Reply-To: <20140907114705.GA10470@abel-laptop>
于 9/7/14, 4:47, Abel Vesa 写道:
> For a while now, I've started studying the power aware scheduling problem.
> And like many other rookies out there I took all the lkml mails related
> and read them all (well, almost all) and I saw that there are some
> debating on the implementation.I even look over the implementation
> proposed of Preeti U Murthy. I also worked (just for fun) for a while on
> some ideas of my own (nothing worth sharing, yet) but I have problem
> understanding the design requirements. Here is one.
>
> Some of you (even Ingo) said that the scheduler should be the one to
> manage the cpu P/C states. In this case the governors of the cpuidle and
> cpufreq would not make any sense anymore. Does that mean they will not
> be a part of this scheduling solution anymore?
CPUIDLE and CPUFREQ are used for cpu power saving when related CPU is
not busy.
Scheduling is coordinate the system load and cpu load. Currently.
Scheduling has no much
idea of CPUIDLE/CPUFREQ status, then may give task to a cpu which in
poor latency or poor
powersaving status. That leads to poor latency and high cost of power.
The power aware scheduling target is to know and coordinate the
cpuidle/cpufreq in scheduling.
Then tasks will be assigned to a cpu unit with better
latency/powersaving consideration.
>
> _______________________________________________
> linaro-kernel mailing list
> linaro-kernel@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-kernel
next prev parent reply other threads:[~2014-09-07 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 11:47 Power Scheduler Design Abel Vesa
2014-09-07 14:29 ` Alex Shi [this message]
2014-09-07 22:58 ` Mike Turquette
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=540C6BCD.70504@linaro.org \
--to=alex.shi@linaro.org \
--cc=abelvesa@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=arjan@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@thegnar.org \
--cc=mike.turquette@linaro.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=sundar.iyer@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
--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