From: Abel Vesa <abelvesa@gmail.com>
To: 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, markgross@thegnar.org,
corbet@lwn.net, catalin.marinas@arm.com, 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: Power Scheduler Design
Date: Sun, 7 Sep 2014 14:47:13 +0300 [thread overview]
Message-ID: <20140907114705.GA10470@abel-laptop> (raw)
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?
next reply other threads:[~2014-09-07 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-07 11:47 Abel Vesa [this message]
2014-09-07 14:29 ` Power Scheduler Design Alex Shi
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=20140907114705.GA10470@abel-laptop \
--to=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 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.