cpuspeed daemon

cpuspeed daemon

[Jeremy Fitzhardinge]

I've been playing around with a little daemon to manage CPU performance
policies.  The intention was not to do some all singing thing which
looks at power source, battery life, running processes, etc, etc, but
something simple to enforce a single policy; if you want to switch
policies, you can do that on the fly.

I've only tried it on my Centrino machine, so it has a fair number of
performance points to play with.  I'm interested to know if it does
anything useful for other chips' power management.

http://www.goop.org/~jeremy/cpuspeed

	J

Re: cpuspeed daemon

[Carl Thompson]

Darn it, you picked the same name I was using for the new version of my
CPUFreq daemon!  (It was called cpufreq, but I thought that was too
confusing).  Well, since I haven't posted it here under the new name yet I
guess I'll have to find another name...

Carl Thompson

Quoting Jeremy Fitzhardinge <jeremy@goop.org>:

> I've been playing around with a little daemon to manage CPU performance
> policies.  The intention was not to do some all singing thing which
> looks at power source, battery life, running processes, etc, etc, but
> something simple to enforce a single policy; if you want to switch
> policies, you can do that on the fly.
>
> I've only tried it on my Centrino machine, so it has a fair number of
> performance points to play with.  I'm interested to know if it does
> anything useful for other chips' power management.
>
> http://www.goop.org/~jeremy/cpuspeed
>
> 	J
>
>
> _______________________________________________
> Cpufreq mailing list
> Cpufreq@www.linux.org.uk
> http://www.linux.org.uk/mailman/listinfo/cpufreq
>
>

Re: cpuspeed daemon

[Jeremy Fitzhardinge]

On Sat, 2003-06-21 at 16:42, Carl Thompson wrote:
> Darn it, you picked the same name I was using for the new version of my
> CPUFreq daemon!  (It was called cpufreq, but I thought that was too
> confusing).  Well, since I haven't posted it here under the new name yet I
> guess I'll have to find another name...

Well, I just changed the name to "speedfreq", so you can have cpuspeed
if you want.

What does your daemon do?

	J

Re: cpuspeed daemon

[Carl Thompson]

Quoting Jeremy Fitzhardinge <jeremy@goop.org>:

> On Sat, 2003-06-21 at 16:42, Carl Thompson wrote:
> > Darn it, you picked the same name I was using for the new version of
> > my CPUFreq daemon!  (It was called cpufreq, but I thought that was too
> > confusing).  Well, since I haven't posted it here under the new name
> > yet I guess I'll have to find another name...
>
> Well, I just changed the name to "speedfreq", so you can have cpuspeed
> if you want.

If you prefer the name "cpuspeed" then you should keep it.  I don't mind
using a different name.  If you really do prefer "speedfreq" then I'll use
"cpuspeed" .

Great minds think alike.  I almost picked "Speed Freq" as my new name before
settling on "Speed Daemon" !

> What does your daemon do?

Pretty much the same thing except mine actually does make policy decisions
and does not yet have a sophisticated plugin infrastructure like yours.
That is planned (though not as complex) but put off until I can get my
laptop to actually run the 2.5 kernel.  Currently it monitors CPU usage,
temperature and the AC adapter and sets the CPU speed accordingly.

I'll try to post an updated version in the next day or so.

> 	J

Carl

Re: cpuspeed daemon

[Jeremy Fitzhardinge]

On Mon, 2003-06-23 at 11:42, Carl Thompson wrote:
> Great minds think alike.  I almost picked "Speed Freq" as my new name before
> settling on "Speed Daemon" !

Heh.  I think the speed puns are inevitable with this kind of thing.

> 
> > What does your daemon do?
> 
> Pretty much the same thing except mine actually does make policy decisions
> and does not yet have a sophisticated plugin infrastructure like yours.

You must be thinking of something other project.  I don't have a plugin
infrastructure, and I'm hoping to never have one.  I'm just trying to do
a simple policy enforcement mechanism, on the grounds that there's
plenty of other people doing policy setting daemon/user interfaces.

	J