On 10/25/10 11:13, Gabriel M. Beddingfield wrote:
On Mon, 25 Oct 2010, Auke Kok wrote:
hehe, yikes!
as Arjan already said, that's terrible from a power consumption perspective.
What you are doing is keeping the CPU out of any C-states whatsoever (by
scheduling to run ever 5ms). Even though you're not making the CPU busy,
you're preventing it from optimally using the C-states available.
A better algorithm would strike a balance between long sleeps (seconds...)
and short bursts of work (even if it runs for quite a while).
This isn't an option for me. PM isn't a top priority for this
application.
However, low-latency audio processing /is/ a top priority.
Being able to switch profiles would give us the best of both
worlds.
in this case you're violating the rule that you should use whatever
scheduler/setting/etc. the system administrator provided to you.
if you have an issue with it, you should probably advertise and document
that your project requires certain kernel features and distro settings
to be turned off and probably mention that your application will
significantly contribute to global warming :)
IOW just provide a README that says that the application requires all
the power savings features to be turned off, which is what you
realistically want.
There's no way to give you what you want without significantly breaking
any form of power saving, so just say that?
Auke
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
