Blame view
Documentation/cpu-freq/governors.txt
9.52 KB
1da177e4c Linux-2.6.12-rc2 |
1 2 3 4 5 6 7 8 9 10 11 |
CPU frequency and voltage scaling code in the Linux(TM) kernel L i n u x C P U F r e q C P U F r e q G o v e r n o r s - information for users and developers - Dominik Brodowski <linux@brodo.de> |
594dd2c98 [PATCH] cpufreq: ... |
12 |
some additions and corrections by Nico Golde <nico@ngolde.de> |
1da177e4c Linux-2.6.12-rc2 |
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
Clock scaling allows you to change the clock speed of the CPUs on the fly. This is a nice method to save battery power, because the lower the clock speed, the less power the CPU consumes. Contents: --------- 1. What is a CPUFreq Governor? 2. Governors In the Linux Kernel 2.1 Performance 2.2 Powersave 2.3 Userspace |
594dd2c98 [PATCH] cpufreq: ... |
29 |
2.4 Ondemand |
537208c80 [PATCH] cpufreq: ... |
30 |
2.5 Conservative |
1da177e4c Linux-2.6.12-rc2 |
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 |
3. The Governor Interface in the CPUfreq Core 1. What Is A CPUFreq Governor? ============================== Most cpufreq drivers (in fact, all except one, longrun) or even most cpu frequency scaling algorithms only offer the CPU to be set to one frequency. In order to offer dynamic frequency scaling, the cpufreq core must be able to tell these drivers of a "target frequency". So these specific drivers will be transformed to offer a "->target" call instead of the existing "->setpolicy" call. For "longrun", all stays the same, though. How to decide what frequency within the CPUfreq policy should be used? That's done using "cpufreq governors". Two are already in this patch -- they're the already existing "powersave" and "performance" which set the frequency statically to the lowest or highest frequency, respectively. At least two more such governors will be ready for addition in the near future, but likely many more as there are various different theories and models about dynamic frequency scaling around. Using such a generic interface as cpufreq offers to scaling governors, these can be tested extensively, and the best one can be selected for each specific use. Basically, it's the following flow graph: |
2fe0ae78c Fix typos in Docu... |
59 |
CPU can be set to switch independently | CPU can only be set |
1da177e4c Linux-2.6.12-rc2 |
60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 |
within specific "limits" | to specific frequencies "CPUfreq policy" consists of frequency limits (policy->{min,max}) and CPUfreq governor to be used / \ / \ / the cpufreq governor decides / (dynamically or statically) / what target_freq to set within / the limits of policy->{min,max} / \ / \ Using the ->setpolicy call, Using the ->target call, the limits and the the frequency closest "policy" is set. to target_freq is set. It is assured that it is within policy->{min,max} 2. Governors In the Linux Kernel ================================ 2.1 Performance --------------- The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq. |
594dd2c98 [PATCH] cpufreq: ... |
89 |
2.2 Powersave |
1da177e4c Linux-2.6.12-rc2 |
90 91 92 93 94 |
------------- The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq. |
594dd2c98 [PATCH] cpufreq: ... |
95 |
2.3 Userspace |
1da177e4c Linux-2.6.12-rc2 |
96 97 98 99 100 101 |
------------- The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory. |
594dd2c98 [PATCH] cpufreq: ... |
102 103 |
2.4 Ondemand ------------ |
a2ffd2751 Fix typos in Docu... |
104 |
The CPUfreq governor "ondemand" sets the CPU depending on the |
594dd2c98 [PATCH] cpufreq: ... |
105 |
current usage. To do this the CPU must have the capability to |
537208c80 [PATCH] cpufreq: ... |
106 107 108 109 110 111 |
switch the frequency very quickly. There are a number of sysfs file accessible parameters: sampling_rate: measured in uS (10^-6 seconds), this is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of |
112124ab0 [CPUFREQ] ondeman... |
112 113 |
around '10000' or more. It's default value is (cmp. with users-guide.txt): transition_latency * 1000 |
112124ab0 [CPUFREQ] ondeman... |
114 115 116 117 118 119 120 |
Be aware that transition latency is in ns and sampling_rate is in us, so you get the same sysfs value by default. Sampling rate should always get adjusted considering the transition latency To set the sampling rate 750 times as high as the transition latency in the bash (as said, 1000 is default), do: echo `$(($(cat cpuinfo_transition_latency) * 750 / 1000)) \ >ondemand/sampling_rate |
537208c80 [PATCH] cpufreq: ... |
121 |
|
e7cbb5b56 Doc: cpufreq: Fix... |
122 |
sampling_rate_min: |
4f4d1ad6e [CPUFREQ] Only se... |
123 124 125 126 |
The sampling rate is limited by the HW transition latency: transition_latency * 100 Or by kernel restrictions: If CONFIG_NO_HZ is set, the limit is 10ms fixed. |
bd74b32b7 Fix documentation... |
127 |
If CONFIG_NO_HZ is not set or nohz=off boot parameter is used, the |
4f4d1ad6e [CPUFREQ] Only se... |
128 129 130 131 132 133 |
limits depend on the CONFIG_HZ option: HZ=1000: min=20000us (20ms) HZ=250: min=80000us (80ms) HZ=100: min=200000us (200ms) The highest value of kernel and HW latency restrictions is shown and used as the minimum sampling rate. |
d91958815 Documentation cle... |
134 |
up_threshold: defines what the average CPU usage between the samplings |
537208c80 [PATCH] cpufreq: ... |
135 136 |
of 'sampling_rate' needs to be for the kernel to make a decision on whether it should increase the frequency. For example when it is set |
292e0041c [CPUFREQ] fix def... |
137 138 |
to its default value of '95' it means that between the checking intervals the CPU needs to be on average more than 95% in use to then |
537208c80 [PATCH] cpufreq: ... |
139 |
decide that the CPU frequency needs to be increased. |
992caacf1 Fix typos in Docu... |
140 141 142 |
ignore_nice_load: this parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilisation' value. When set to '1', the processes that are |
537208c80 [PATCH] cpufreq: ... |
143 |
run with a 'nice' value will not count (and thus be ignored) in the |
992caacf1 Fix typos in Docu... |
144 |
overall usage calculation. This is useful if you are running a CPU |
537208c80 [PATCH] cpufreq: ... |
145 146 147 |
intensive calculation on your laptop that you do not care how long it takes to complete as you can 'nice' it and prevent it from taking part in the deciding process of whether to increase your CPU frequency. |
5b95364f6 [CPUFREQ] Add doc... |
148 149 150 151 152 153 154 155 156 157 |
sampling_down_factor: this parameter controls the rate at which the kernel makes a decision on when to decrease the frequency while running at top speed. When set to 1 (the default) decisions to reevaluate load are made at the same interval regardless of current clock speed. But when set to greater than 1 (e.g. 100) it acts as a multiplier for the scheduling interval for reevaluating load when the CPU is at its top speed due to high load. This improves performance by reducing the overhead of load evaluation and helping the CPU stay at its top speed when truly busy, rather than shifting back and forth in speed. This tunable has no effect on behavior at lower speeds/lower CPU loads. |
537208c80 [PATCH] cpufreq: ... |
158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 |
2.5 Conservative ---------------- The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of: freq_step: this describes what percentage steps the cpu freq should be increased and decreased smoothly by. By default the cpu frequency will increase in 5% chunks of your maximum cpu frequency. You can change this value to anywhere between 0 and 100 where '0' will effectively lock your CPU at a speed regardless of its load whilst '100' will, in theory, make it behave identically to the "ondemand" governor. down_threshold: same as the 'up_threshold' found for the "ondemand" governor but for the opposite direction. For example when set to its default value of '20' it means that if the CPU usage needs to be below 20% between samples to have the frequency decreased. |
1da177e4c Linux-2.6.12-rc2 |
181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 |
3. The Governor Interface in the CPUfreq Core ============================================= A new governor must register itself with the CPUfreq core using "cpufreq_register_governor". The struct cpufreq_governor, which has to be passed to that function, must contain the following values: governor->name - A unique name for this governor governor->governor - The governor callback function governor->owner - .THIS_MODULE for the governor module (if appropriate) The governor->governor callback is called with the current (or to-be-set) cpufreq_policy struct for that CPU, and an unsigned int event. The following events are currently defined: CPUFREQ_GOV_START: This governor shall start its duty for the CPU policy->cpu CPUFREQ_GOV_STOP: This governor shall end its duty for the CPU policy->cpu CPUFREQ_GOV_LIMITS: The limits for CPU policy->cpu have changed to policy->min and policy->max. If you need other "events" externally of your driver, _only_ use the cpufreq_governor_l(unsigned int cpu, unsigned int event) call to the CPUfreq core to ensure proper locking. The CPUfreq governor may call the CPU processor driver using one of these two functions: int cpufreq_driver_target(struct cpufreq_policy *policy, unsigned int target_freq, unsigned int relation); int __cpufreq_driver_target(struct cpufreq_policy *policy, unsigned int target_freq, unsigned int relation); target_freq must be within policy->min and policy->max, of course. What's the difference between these two functions? When your governor still is in a direct code path of a call to governor->governor, the per-CPU cpufreq lock is still held in the cpufreq core, and there's no need to lock it again (in fact, this would cause a deadlock). So use __cpufreq_driver_target only in these cases. In all other cases (for example, when there's a "daemonized" function that wakes up every second), use cpufreq_driver_target to lock the cpufreq per-CPU lock before the command is passed to the cpufreq processor driver. |