Tomasz Chmielewski wrote:
Clock throttling is not likely to save your battery, unless you have
tasks that are running at 100% CPU for an unlimited time or
something, and you force your CPU to throttle. Normally most people
have tasks that run and then the CPU idles - loading an email,
displaying a web page, etc. Clock throttling will just make these
tasks utilize the CPU for a longer time proportional to the amount
clock throttling and therefore negate any gains in battery usage.
Aren't you forgetting about CPUfreq governors? Which mean: use the
maximum CPU frequency when the system is busy, throttle down (or lower
voltage) when the system is idle.
So yes, throttling will save the battery.
We are talking about throttling (i.e. P4 clockmod) not CPU frequency
scaling. Clock modulation does not reduce the clock speed, it just
basically forces the CPU to halt on a certain duty cycle. If the CPU is
already idle this has no effect and won't save any power.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
