* Re: [2.6. PATCH] Missing default governor choices
@ 2004-08-29 12:32 Dominik Brodowski
2004-08-30 17:15 ` GoatZilla
0 siblings, 1 reply; 2+ messages in thread
From: Dominik Brodowski @ 2004-08-29 12:32 UTC (permalink / raw)
To: goatzilla, cpufreq
> What's the reason for the powersave governor not being selectable as
> default?
Because it doesn't matter much:
- performance is available during boot so that CPUs starting up at less than
100% can be boosted to full performance very soon.
- userspace is available to keep the CPU speed at what it was at boot, and
to allow existing userspace-based setups to work [it offers an equivalent
interface compared to the one of the old 2.4. cpufreq interface]
All other settings [including min/max ranges, governor for "continuing" use] can
and should be done by either a startup script and/or a userspace daemon.
Dominik
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [2.6. PATCH] Missing default governor choices
2004-08-29 12:32 [2.6. PATCH] Missing default governor choices Dominik Brodowski
@ 2004-08-30 17:15 ` GoatZilla
0 siblings, 0 replies; 2+ messages in thread
From: GoatZilla @ 2004-08-30 17:15 UTC (permalink / raw)
To: cpufreq
Is there something wrong with wanting powersave activated as soon as possible?
If a user wants performance at bootup, he can choose the performance
governor as default.
If a user wants to maintain the startup speed at bootup, he can choose
the userspace governor as default.
If a user wants powersaving at bootup... Too bad, go write a startup script?
It's not a big issue; I wrote a startup script for it myself. I was
just left wondering why I had to write a startup script in the first
place.
On Sun, 29 Aug 2004 14:32:00 +0200, Dominik Brodowski
<linux@dominikbrodowski.de> wrote:
> > What's the reason for the powersave governor not being selectable as
> > default?
>
> Because it doesn't matter much:
> - performance is available during boot so that CPUs starting up at less than
> 100% can be boosted to full performance very soon.
> - userspace is available to keep the CPU speed at what it was at boot, and
> to allow existing userspace-based setups to work [it offers an equivalent
> interface compared to the one of the old 2.4. cpufreq interface]
>
> All other settings [including min/max ranges, governor for "continuing" use] can
> and should be done by either a startup script and/or a userspace daemon.
>
> Dominik
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-08-30 17:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-08-29 12:32 [2.6. PATCH] Missing default governor choices Dominik Brodowski
2004-08-30 17:15 ` GoatZilla
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.