From 34edd4e2a7335cbddd67ed8270b4d93effeeed2a Mon Sep 17 00:00:00 2001 From: Thomas Gebert Date: Tue, 7 Oct 2025 15:35:08 +0200 Subject: [PATCH] Adopt README for script change --- cpupower/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpupower/readme.md b/cpupower/readme.md index ffb0de3..a9e2b21 100644 --- a/cpupower/readme.md +++ b/cpupower/readme.md @@ -67,7 +67,7 @@ ansible -b storage\_nodes -m shell -a "systemctl enable --now cpupower.service" #### Sidenotes ##### cpupower.sh -The script uses *cpupower idle-set --disable-by-latency*, which is out of convenience since this option allows to disable all C-States that take more time than specified at once. While just using disable just disables a single C-States but does not disable deeper one. E.g. (based on the example from [cpupower idle-info](#cpupowerandc-stateconfiguration-cpupowe)) *cpupower idle-set --disable 4* would disable C1E status but would leave C6 status active... +The script can be configured to either use a C-State as MAX, which is preferred or by latency. Both can be configured in /etc/default/cpupower. ## How To Check the actual status To check the actual status of the CPU power settings it is recommended to query it directly with *cpupower*.