From: Daniel P. <d.p...@gm...> - 2005-04-20 21:05:59
|
Hello Todd, On 4/15/05, Todd Poynor <tp...@mv...> wrote: >=20 > Hello Daniel -- I've been too busy as of late to look into this in > depth, but I am curious to hear people's requests for, or experience > with, such ability to automatically assign DPM task states at exec time > according to custom rules (such as by command name, as with this patch). Admittedly, most folks using DPM are using it in tightly-controlled > mobile phone / PDA consumer electronics devices, where a main menu > application can make these decisions according to its own logic, instead > of a general-purpose interactive desktop/server environment with no > central control over execution of apps.=20 OK, I Agree but nonetheless this patch can be used by Centrino users who can assign task states to some process that will likely run. So, after assigning some normally used applications one can have power savings assured after configuring it in initscripts.=20 I don't know why DPM has support for centrino as it is not likely to be use= d for mobile phone and PDA consumer goods, but if one of the reasons are broaden the DPM usage sometimes we could look to that side. Even in small linux systems this idea can be used to have a default=20 and starting configuration for dpm, although small systems requiring power savings needs much more than this. Ways of applying heuristics to > power management characteristics of new processes without searching a > list at each process exec would be a plus, although custom ELF header > extensions and the like are messy as well. Thanks, That work was made to have some experience and knowledge of DPM, now I'm looking for new ideas to try to have improvements and suggestions to DPM. And I think, as well, that applying heuristics to process=20 characteristics may lead to great improvements in power management. I think of some simple calculations to have data to help to decide to which= =20 task-state should a process be moved. To a given process calculate some values like: 1) CPU usage in last minute/ Total CPU=20 2) I/O usage in last minute, how much time blocked - here the type of I/O must be of interest, network more important than display... 3) Process priority 4) Some value from the system manager (which spawns controlled apps) 5) ... Actually I'm looking for these metrics that could help to decide. It seems that all of these should be implemented in user-space, to run as a daemon unless one need to export some information from kernel.=20 OK. That is it. If you have some pointers to follow I'm open to that. Daniel --=20 10LE - Linux Nokia Institute of Tecnology - INdT Manaus - Brazil |