On 3/18/2010 17:46, Chad Spears wrote:
I was curious to see who is working on power tuning in the core development. This is an area I will be interested in as soon as I get a copy of meego. Is the focus mostly on mobiles?
I suspect I and a bunch of others will end up involved in that. The good news, to me at least, is that power tuning by and large is universal... it is extremely rare (in fact I cannot think of anything right now) that something that's good for one type of device for power, is bad for any other type. there are a set of universal things for power, and then some device specific ones 1) Do not waste performance. A 10% waste in performance tends to be a similar loss in power. (this is good news, many people know how to tune for performance already) 2) Mind your wakeups, and use all the available techniques to reduce them. Eg run powertop and fix anything that shows up. Fix software to not do stupid polling. Use range timers. etc etc 3) Have high quality, good device drivers. Device drivers own their device's power, and a good driver makes all the difference in the world for the final power result. 4) Keep an eye on background activity... any percent of CPU that you steal in the background is also power that you steal. "timechart" is a good tool to chase these down in general the "one bad guy can ruin it all" rule applies.... there are some device specific items to tune, the most obvious one I can think of is the policy for CPU frequency/voltage, and generally the CPU vendor is expected to provide good code to Linux for this. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
