... | @@ -27,6 +27,11 @@ likwid-setFrequencies can only be used in conjunction with the `acpi-cpufreq` ke |
... | @@ -27,6 +27,11 @@ likwid-setFrequencies can only be used in conjunction with the `acpi-cpufreq` ke |
|
-y/--max freq Set maximal CPU frequency
|
|
-y/--max freq Set maximal CPU frequency
|
|
--umin freq Set minimal Uncore frequency
|
|
--umin freq Set minimal Uncore frequency
|
|
--umax freq Set maximal Uncore frequency
|
|
--umax freq Set maximal Uncore frequency
|
|
|
|
|
|
|
|
-reset Set governor 'performance', set minimal and maximal frequency to
|
|
|
|
the CPU limits and deactivate turbo
|
|
|
|
-ureset Set Uncore frequencies to its min and max limits
|
|
|
|
|
|
```
|
|
```
|
|
|
|
|
|
## Usage
|
|
## Usage
|
... | @@ -82,6 +87,12 @@ Prints all available affinity domains, see [[likwid-pin|likwid-pin]] Wiki page. |
... | @@ -82,6 +87,12 @@ Prints all available affinity domains, see [[likwid-pin|likwid-pin]] Wiki page. |
|
### Manipulating Uncore frequency on Intel CPUs
|
|
### Manipulating Uncore frequency on Intel CPUs
|
|
Some Intel CPUs provide the possibility to change the Uncore frequency. You can use the `--umin` and `--umax` command line options to set it. One problem with the Uncore frequency is that the minimal and maximal frequency limits are not readable in all system configurations. Therefore LIKWID defines a range of supported frequencies. To be sure that the frequency you adjusted as requested, measure the `UNCORE_CLOCK` event using `likwid-perfctr`.
|
|
Some Intel CPUs provide the possibility to change the Uncore frequency. You can use the `--umin` and `--umax` command line options to set it. One problem with the Uncore frequency is that the minimal and maximal frequency limits are not readable in all system configurations. Therefore LIKWID defines a range of supported frequencies. To be sure that the frequency you adjusted as requested, measure the `UNCORE_CLOCK` event using `likwid-perfctr`.
|
|
|
|
|
|
|
|
### Resetting frequencies
|
|
|
|
Starting with LIKWID 4.3.2, it is possible to reset the CPU and Uncore frequencies to its full range to return to a defined state. There are different switches for CPU frequencies (`-reset`) and Uncore frequencies (`-ureset`):
|
|
|
|
|
|
|
|
- `-reset`: Change CPU frequencies to its minimal and maximal frequencies. If not specified, the turbo is deactivated and the maximum non-turbo frequency selected. The turbo reset setting can be set with `-t <0|1>`. The governor is switched back to the last on the list of available governors (`-m`) or to the one specified (`-g <gov>`).
|
|
|
|
- `-ureset`: Change the Uncore frequencies to minimum (lowest available CPU frequency, first at `likwid-setFrequencies -l`) and to maximum (highest turbo frequency if only a single core is running, `C0` at `likwid-powermeter -i`)
|
|
|
|
|
|
## Configuration of the setFreq daemon
|
|
## Configuration of the setFreq daemon
|
|
|
|
|
|
Since the daemon process `likwid-setFreq` requires higher privileges than the control script likwid-setFrequency. There are two methods to grant this to the daemon:
|
|
Since the daemon process `likwid-setFreq` requires higher privileges than the control script likwid-setFrequency. There are two methods to grant this to the daemon:
|
... | | ... | |