From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Salman Qazi <sqazi@google.com>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Michael Rubin <mrubin@google.com>,
Taliver Heath <taliver@google.com>
Subject: Re: RFC: A proposal for power capping through forced idle in the Linux Kernel
Date: Tue, 22 Dec 2009 20:48:24 +0100 [thread overview]
Message-ID: <1261511304.4937.116.camel@laptop> (raw)
In-Reply-To: <20091214161922.6f252492@infradead.org>
On Mon, 2009-12-14 at 16:19 -0800, Arjan van de Ven wrote:
> I like the general idea, I have one request (that I didn't see quite in
> your explanation): Please make sure that all cpus in the system do
> their idle injection at the same time, so that memory can go into power
> saving mode as well during this time etc etc...
And then you're going to ask that it scales too, right? :-)
Gang-scheduling is inherently non scalable, be it for idle time or not.
next prev parent reply other threads:[~2009-12-22 19:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 23:11 RFC: A proposal for power capping through forced idle in the Linux Kernel Salman Qazi
2009-12-14 23:21 ` Andi Kleen
2009-12-14 23:51 ` tytso
2009-12-14 23:51 ` tytso
2009-12-15 0:42 ` Salman Qazi
2009-12-15 0:42 ` Salman Qazi
2009-12-22 19:48 ` Peter Zijlstra
2009-12-22 19:48 ` Peter Zijlstra
2009-12-14 23:21 ` Andi Kleen
2009-12-15 0:19 ` Arjan van de Ven
2009-12-15 0:19 ` Arjan van de Ven
2009-12-15 0:36 ` Salman Qazi
2009-12-15 0:36 ` Salman Qazi
2009-12-15 1:06 ` Arjan van de Ven
2009-12-15 20:15 ` Salman Qazi
2009-12-17 11:01 ` Arjan van de Ven
2009-12-17 11:01 ` Arjan van de Ven
2009-12-15 20:15 ` Salman Qazi
2009-12-15 1:06 ` Arjan van de Ven
2009-12-15 10:29 ` Vaidyanathan Srinivasan
2009-12-15 11:50 ` Vaidyanathan Srinivasan
2009-12-15 11:50 ` Vaidyanathan Srinivasan
2009-12-15 21:00 ` Salman Qazi
2009-12-15 21:00 ` Salman Qazi
2009-12-15 20:50 ` Salman Qazi
2009-12-15 20:50 ` Salman Qazi
2009-12-15 10:29 ` Vaidyanathan Srinivasan
2009-12-22 19:48 ` Peter Zijlstra
2009-12-22 19:48 ` Peter Zijlstra [this message]
2009-12-22 19:57 ` Arjan van de Ven
2009-12-22 19:57 ` Arjan van de Ven
2009-12-18 17:04 ` Pavel Machek
2009-12-22 21:10 ` Salman Qazi
2009-12-22 21:10 ` Salman Qazi
2009-12-23 9:49 ` Pavel Machek
2009-12-23 9:49 ` Pavel Machek
2009-12-18 17:04 ` Pavel Machek
2009-12-21 8:57 ` Pavel Machek
2009-12-21 8:57 ` Pavel Machek
2009-12-22 21:15 ` Salman Qazi
2009-12-22 21:15 ` Salman Qazi
2009-12-23 9:52 ` Pavel Machek
2009-12-23 9:52 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-12-14 23:11 Salman Qazi
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=1261511304.4937.116.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mrubin@google.com \
--cc=sqazi@google.com \
--cc=taliver@google.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 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.