From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Gregory Haskins <ghaskins@novell.com>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
Jon Masters <jonathan@jonmasters.org>
Subject: Re: sched: deep power-saving states
Date: Wed, 22 Oct 2008 21:49:52 +0200 [thread overview]
Message-ID: <1224704992.20069.71.camel@twins> (raw)
In-Reply-To: <20081022073616.5eb150fa@infradead.org>
On Wed, 2008-10-22 at 07:36 -0700, Arjan van de Ven wrote:
> On Wed, 22 Oct 2008 10:26:49 -0400
> Gregory Haskins <ghaskins@novell.com> wrote:
> steps, so it'll be
> > > faster)
> >
> > [Adding Peter Zijlstra to the thread]
> >
> > Ah, yes of course! That makes sense. So I have to admit I am fairly
> > ignorant of the ACPI C-state stuff, so I just read up on it. In the
> > context of what you said, it makes perfect sense to me now.
> >
> > IIUC, the OS selects which C-state it will enter at idle points based
> > on some internal criteria (TBD). All we have to do is remap the
> > cpupri "IDLE" state to something like IDLE-C1, IDLE-C2, ..., IDLE-Cn
> > and have the cpupri map get updated coincident with the pm_idle()
> > call. Then the scheduler will naturally favor cores that are in
> > lighter sleep over cores in deep sleep.
> >
> > I am not sure if this is exactly what you were getting at during the
> > conf, since it doesnt really consider deep-sleep latency times
> > directly. But I think this is a step in the right direction.
>
> it for sure is a step in the right direction.
> the actual exit costs are an optional parameter in this sense,
> the steps between C states are non-linear (more like exponential)
> so knowing the actual numbers could be used. but even if you don't
> use it, it still makes sense and is a very good first order behavior.
This still leaves us with the worst case IRQ response as given by the
deepest C state. Which might be un-desirable.
jcm was, once upon a time, working on dynamically changing the idle
routine, so that people who care about wakeup latency can run idle=poll
while their application runs, and the acpi C state stuff when nobody
cares.
This could of course then be tied into the PM QoS stuff Mark has been
doing.
Fact of life is, for some RT apps, anything but idle=poll is too much.
But yes, when C states are in play, it makes sense to try and wake a cpu
that's not deep over a very deep idle one.
next prev parent reply other threads:[~2008-10-22 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 13:42 sched: deep power-saving states Gregory Haskins
2008-10-22 13:47 ` Arjan van de Ven
2008-10-22 14:05 ` Gregory Haskins
2008-10-22 14:07 ` Arjan van de Ven
2008-10-22 14:26 ` Gregory Haskins
2008-10-22 14:36 ` Arjan van de Ven
2008-10-22 19:49 ` Peter Zijlstra [this message]
2008-10-22 19:55 ` Arjan van de Ven
2008-10-22 20:05 ` Peter Zijlstra
2008-10-22 20:12 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2008-10-22 13:44 Gregory Haskins
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=1224704992.20069.71.camel@twins \
--to=peterz@infradead.org \
--cc=arjan@infradead.org \
--cc=ghaskins@novell.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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