1 |
Apparently, though unproven, at 18:34 on Tuesday 10 May 2011, James did opine |
2 |
thusly: |
3 |
|
4 |
> Alan McKinnon <alan.mckinnon <at> gmail.com> writes: |
5 |
> > otherwise. Just enable ondemand, disable everything else, and et the |
6 |
> > kernel |
7 |
> |
8 |
> > get on with doing what it does best: |
9 |
> So this is what you are saying? |
10 |
> |
11 |
> |
12 |
> [*] CPU Frequency scaling │ │ |
13 |
> │ │ [*] Enable CPUfreq debugging │ │ |
14 |
> │ │ <*> CPU frequency translation statistics │ │ |
15 |
> │ │ [ ] CPU frequency translation statistics details │ │ |
16 |
> │ │ Default CPUFreq governor (performance) ---> │ │ |
17 |
> │ │ -*- 'performance' governor │ │ |
18 |
> │ │ < > 'powersave' governor │ │ |
19 |
> │ │ < > 'userspace' governor for userspace frequency scaling│ │ |
20 |
> │ │ <*> 'ondemand' cpufreq policy governor │ │ |
21 |
> │ │ < > 'conservative' cpufreq governor │ │ |
22 |
> │ │ *** CPUFreq processor drivers *** │ │ |
23 |
> │ │ < > Processor Clocking Control interface driver │ │ |
24 |
> │ │ <*> ACPI Processor P-States driver │ │ |
25 |
> │ │ < > AMD Opteron/Athlon64 PowerNow! │ │ |
26 |
> │ │ < > Intel Enhanced SpeedStep (deprecated) │ │ |
27 |
> │ │ < > Intel Pentium 4 clock modulation |
28 |
|
29 |
Mostly. |
30 |
|
31 |
The performance governor cannot be disabled (-*-) so it is always selected, |
32 |
and the default should be set to ondemand. |
33 |
|
34 |
The above is for personal workstations, laptops etc. For servers requiring |
35 |
decent throughput and where power and cooling is not an issue, one would use a |
36 |
different approach of course. |
37 |
|
38 |
-- |
39 |
alan dot mckinnon at gmail dot com |