On Wed, Jun 30, 2010 at 03:34:14PM -0400, Ted Unangst wrote: > On Wed, Jun 30, 2010 at 3:23 PM, Luis Henriques <luis.hen...@gmail.com> > wrote: > > Probably, a silly question, but here it goes: > > > > With this patch, I will not be able to set the perflevel to, say, 50% and > > keep the system using that performance level forever. Is this correct? > > I guess that with current apmd we are able to do this. > > > > If both of these two statements are true (maybe they are not!), we should > > also have a mechanism to disable this code (either at runtime or compile > > time). > > You are correct, but I wonder why you would ever want a machine only > running at 50% all the time. When it is busy, it's still slow, and > when it's not, it's still using power.
This only makes sense once you think of it or have it mentioned to you, as I well know. ;-) > We are thinking that states other than 0 and 100 are not very useful. This is true when you have a bucket of work to do, like compiling a kernel or something. It's less true when you are playing media, where a 20 minute video takes 20 minutes regardless of cpu at 100% or cpu at 30%. > But this is not the final diff. It will probably have some means of > control eventually, until then, it'd be nice if people evaluated if > this meets their needs. :) -- Darrin Chandler | Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
