Re: RFC: A proposal for power capping through forced idle in the Linux Kernel

[Salman Qazi]

On Fri, Dec 18, 2009 at 9:04 AM, Pavel Machek <pavel@xxxxxx> 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?

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

>
> Better example would be 'make video so choppy that expected battery
> time rises over length ov movie.
>
> (And yes, this would have been useful for me on notebook with failed
> fan and ineffective throttling).
>
>
>                                                                Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/