public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Peter Zijlstra <peterz@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:57:43 +0100	[thread overview]
Message-ID: <20091222205743.4b6cf677@infradead.org> (raw)
In-Reply-To: <1261511304.4937.116.camel@laptop>

On Tue, 22 Dec 2009 20:48:24 +0100
Peter Zijlstra <peterz@infradead.org> wrote:

> 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.

well... there's many ways to do this... one option is to agree, ahead
of time, which jiffies values you're going to do the idle thing on.
Say every 100 jiffies where jiffies % 100 is 0....

then the scalability thing isn't a big deal.. and you still do it all
at the same time. Or at least "enough" at the same time for it to not
matter



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-12-22 19:55 UTC|newest]

Thread overview: 22+ 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-15  0:42     ` Salman Qazi
2009-12-22 19:48     ` Peter Zijlstra
2009-12-15  0:19 ` Arjan van de Ven
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-15 10:29     ` Vaidyanathan Srinivasan
2009-12-15 11:50       ` Vaidyanathan Srinivasan
2009-12-15 21:00         ` Salman Qazi
2009-12-15 20:50       ` Salman Qazi
2009-12-22 19:48   ` Peter Zijlstra
2009-12-22 19:57     ` Arjan van de Ven [this message]
2009-12-18 17:04 ` Pavel Machek
2009-12-22 21:10   ` Salman Qazi
2009-12-23  9:49     ` Pavel Machek
2009-12-21  8:57 ` Pavel Machek
2009-12-22 21:15   ` Salman Qazi
2009-12-23  9:52     ` Pavel Machek

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=20091222205743.4b6cf677@infradead.org \
    --to=arjan@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mrubin@google.com \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox