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 22:05:25 +0200 [thread overview]
Message-ID: <1224705925.20069.76.camel@twins> (raw)
In-Reply-To: <20081022125508.2ccea6e1@infradead.org>
On Wed, 2008-10-22 at 12:55 -0700, Arjan van de Ven wrote:
> On Wed, 22 Oct 2008 21:49:52 +0200
> Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > This still leaves us with the worst case IRQ response as given by the
> > deepest C state. Which might be un-desirable.
>
> that's a different problem in a different problem space.
Ah right, so the only point was trying to wake shallow cpus so as to try
and let deep cpus idle longer?
> > 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.
>
> in fact you already have this *exactly* today; this isn't future
> technology.
Interesting, what knob do I turn to get idle=poll dynamically?
next prev parent reply other threads:[~2008-10-22 20:05 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
2008-10-22 19:55 ` Arjan van de Ven
2008-10-22 20:05 ` Peter Zijlstra [this message]
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=1224705925.20069.76.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