@@ -268,6 +268,7 @@ The following policy options exist for the static `CPUManager` policy:
268
268
* `distribute-cpus-across-numa` (alpha, hidden by default) (1.23 or higher)
269
269
* `align-by-socket` (alpha, hidden by default) (1.25 or higher)
270
270
* `distribute-cpus-across-cores` (alpha, hidden by default) (1.31 or higher)
271
+ * `strict-cpu-reservation` (alpha, hidden by default) (1.32 or higher)
271
272
272
273
If the `full-pcpus-only` policy option is specified, the static policy will always allocate full physical cores.
273
274
By default, without this option, the static policy allocates CPUs using a topology-aware best-fit allocation.
@@ -318,7 +319,6 @@ the benefit of reducing contention diminishes. Conversely, default behavior
318
319
can help in reducing inter-core communication overhead, potentially providing
319
320
better performance under high load conditions.
320
321
321
-
322
322
The `full-pcpus-only` option can be enabled by adding `full-pcpus-only=true` to
323
323
the CPUManager policy options.
324
324
Likewise, the `distribute-cpus-across-numa` option can be enabled by adding
@@ -334,3 +334,12 @@ The `distribute-cpus-across-cores` option can be enabled by adding
334
334
` distribute-cpus-across-cores=true` to the `CPUManager` policy options.
335
335
It cannot be used with `full-pcpus-only` or `distribute-cpus-across-numa` policy
336
336
options together at this moment.
337
+
338
+ The `strict-cpu-reservation` option can be enabled by adding `strict-cpu-reservation=true` to
339
+ the CPUManager policy options.
340
+
341
+ If the `strict-cpu-reservation` policy option is enabled, the static policy will not allow
342
+ workloads to use the CPU cores specified in `reservedSystemCPUs`.
343
+ The `reservedSystemCPUs` defines an explicit CPU set for OS system daemons and kubernetes
344
+ system daemons. More details of this parameter can be found on the
345
+ [Explicitly Reserved CPU List](/docs/tasks/administer-cluster/reserve-compute-resources) page.
0 commit comments