Merge pull request #55468 from amolnar-rh/TELCODOCS-1169

TELCODOCS-1169: Corrections to power saving configuration docs

Author: mburke5678

modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc

@@ -339,7 +339,7 @@ When you configure a node with a power saving configuration, you must configure
 
 By disabling P-states and C-states at the pod level, you can configure high priority workloads for best performance and lowest latency.
 
-.Power saving configurations
+.Configuration for high priority workloads
 [cols="1,2", options="header"]
 |====
 |Annotation
@@ -348,7 +348,7 @@ By disabling P-states and C-states at the pod level, you can configure high prio
 a|[source,yaml]
 ----
 annotations:
-  cpu-c-states.crio.io: "enable"
+  cpu-c-states.crio.io: "disable"
   cpu-freq-governor.crio.io: "<governor>"
 ----
 |Provides the best performance for a pod by disabling C-states and specifying the governor type for CPU scaling. The `performance` governor is recommended for high priority workloads.
@@ -416,12 +416,11 @@ spec:
       [sysfs]
       /sys/devices/system/cpu/intel_pstate/max_perf_pct = <x> <1>
 ----
-<1> The `max_perf_pct` controls the maximum frequency the `cpufreq` driver is allowed to set as a percentage of the maximum supported cpu frequency. This value applies to all CPUs. You can check the maximum supported frequency in `/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`.
+<1> The `max_perf_pct` controls the maximum frequency the `cpufreq` driver is allowed to set as a percentage of the maximum supported cpu frequency. This value applies to all CPUs. You can check the maximum supported frequency in `/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`. As a starting point, you can use a percentage that caps all CPUs at the `All Cores Turbo` frequency. The `All Cores Turbo` frequency is the frequency that all cores will run at when the cores are all fully occupied.
 
-
-. Add the desired annotations to your pods. The annotations override the `default` settings.
+. Add the desired annotations to your high priority workload pods. The annotations override the `default` settings.
 +
-.Example power saving annotation
+.Example high priority workload annotation
 [source,yaml]
 ----
 apiVersion: v1
@@ -430,7 +429,7 @@ metadata:
   ...
   annotations:
     ...
-    cpu-c-states.crio.io: "enable"
+    cpu-c-states.crio.io: "disable"
     cpu-freq-governor.crio.io: "<governor>"
     ...
   ...