>
> You can query the system to find out what the current settings are, and
> also change the current settings to optimize for best CPU throughput or
> best power savings.
IMHO simple user level tool can do it.

something like
while(1) {
 int cpuload=check_average_cpu_usage();
 sleep(5);
 if(cpuload<0.9)
  lower_cpu_clock();
 if(cpuload>0.95)
  higher_cpu_clock();}

the average should be for about 5-10 secs.

> I want to add suport for this to NetBSD, and I'm wondering what the
> best way to do it is. FreeBSD did this by adding sysctl variables. I've
> currently got a device driver and userland program for doing queries.
> Which way is better? Or should I be doing something else entirely?
>
> Keeping in mind that LongRun is also implemented on multi-user
> servers (Crusoes are used in high-CPU-density server farms) as well as
> more-or-less single-user notebooks, access control is vital. (It shouln't
> be possible for any random user to go and slow down the system.)
>
> cjs
> --
> Curt Sampson  <cjs@cynic.net>   +81 3 5778 0123   http://www.netbsd.org
>     Don't you know, in this new Dark Age, we're all light.  --XTC
>