From: Arjan van de Ven <arjan@linux.intel.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Rik van Riel <riel@redhat.com>, Jeremy Eder <jeder@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"youquan.song@intel.com" <youquan.song@intel.com>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"len.brown@intel.com" <len.brown@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: RFC: revert request for cpuidle patches e11538d1 and 69a37bea
Date: Mon, 29 Jul 2013 09:04:35 -0700 [thread overview]
Message-ID: <51F69293.1060308@linux.intel.com> (raw)
In-Reply-To: <20130729160106.GA13311@e102568-lin.cambridge.arm.com>
On 7/29/2013 9:01 AM, Lorenzo Pieralisi wrote:
>
>> Coupled C states on this level are a PAIN in many ways, and tend to totally suck for power
>> due to this and the general "too much is active" reasons.
>
> I think the trend is moving towards core gating, which resembles a lot to what
> x86 world does today. Still, the interaction between menu governor and
> cluster states has to be characterized and that's we are doing at the
> moment.
I suspect that we (Linux) need a different governor than menu for the coupled case.
Fundamentally you're going to need different algorithms that are much closer tied
to the behavior of the specific hardware; the current menu governor uses an abstract
and simple hardware model (fully independent).
For specific hardware that deviates from the model, something different is clearly needed.
It's an open question for me if just the predictor is the part that
you split out, or if the whole governor needs to be split out.
(but frankly, if you take the predictor out of the menu governor, not a whole lot is left)
next prev parent reply other threads:[~2013-07-29 16:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 17:33 RFC: revert request for cpuidle patches e11538d1 and 69a37bea Jeremy Eder
2013-07-26 18:13 ` Rik van Riel
2013-07-26 18:27 ` Arjan van de Ven
2013-07-26 18:29 ` Rik van Riel
2013-07-26 21:48 ` Rafael J. Wysocki
2013-07-27 0:36 ` Rafael J. Wysocki
2013-07-27 6:22 ` Len Brown
2013-07-27 12:10 ` Rafael J. Wysocki
2013-07-27 7:11 ` Daniel Lezcano
2013-07-29 11:49 ` Arjan van de Ven
2013-07-29 13:12 ` Arjan van de Ven
2013-07-29 14:14 ` Lorenzo Pieralisi
2013-07-29 14:29 ` Arjan van de Ven
2013-07-29 16:01 ` Lorenzo Pieralisi
2013-07-29 16:04 ` Arjan van de Ven [this message]
2013-07-27 6:43 ` Daniel Lezcano
2013-07-30 3:57 ` Youquan Song
2013-07-29 16:59 ` Jeremy Eder
2013-08-02 18:19 ` Jeremy Eder
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=51F69293.1060308@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=jeder@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=riel@redhat.com \
--cc=vincent.guittot@linaro.org \
--cc=youquan.song@intel.com \
/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).