public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Salman Qazi <sqazi@google.com>
Cc: 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: Wed, 23 Dec 2009 10:49:05 +0100	[thread overview]
Message-ID: <20091223094905.GC24181@elf.ucw.cz> (raw)
In-Reply-To: <4352991a0912221310k40f42498nba2081011398c7e@mail.gmail.com>

On Tue 2009-12-22 13:10:36, Salman Qazi wrote:
> On Fri, Dec 18, 2009 at 9:04 AM, Pavel Machek <pavel@ucw.cz> wrote:
> > Hi
> >
> >
> >> Why not use voltage and frequency scaling?
> >>
> >> Forced Idle Injection is more effective[1] and more widely available.
> >> Even with voltage and frequency scaling, interpolation is needed
> >> between the available settings.  So, if we did use voltage and
> >
> > It is only more efficient on new hardware.
> >
> > You should also explain 'why not throttling' because that is actually
> > designed for power capping.
> 
> Do you mean t-states?

Yes.

> >> Application to Laptops and Cellphones:
> >>
> >> Imagine being in a tent in Death Valley with a laptop.  You are bored,
> >> and you want to watch a movie.  However, you also want to do your best
> >> to make the battery last and watch as much of the movie as possible.
> >> Forced idle power capping is a solution.  If your machine has a knob
> >> that allows you to control the available power, you can turn that knob
> >> until your video starts getting choppy.  And then, turn the knob back
> >
> > That's bad example. Video player should already sleep between frames.
> 
> Yes, the video player should sleep.  However, there will be other
> things running.  And certainly, it is possible to cap the power and
> discriminate so that those things are prevented from running while the
> video player is allowed to run with minimal latency impact.

I don't see how it would work without much of extra setup. Lets say
your windowmanager wants to do some work, and you starve it
indefinitely?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-12-23  9:49 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
2009-12-18 17:04 ` Pavel Machek
2009-12-22 21:10   ` Salman Qazi
2009-12-23  9:49     ` Pavel Machek [this message]
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=20091223094905.GC24181@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox