Skip to content

Commit d138233

Browse files
authored
Merge pull request #38471 from aireilly/gh#36355
gh#36355 - Clarify isolated and reserved CPUs information
2 parents 95bf122 + 588e9e2 commit d138233

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

modules/configuring_hyperthreading_for_a_cluster.adoc

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -64,16 +64,21 @@ $ cat /sys/devices/system/cpu/cpu0/topology/thread_siblings_list
6464
0-4
6565
----
6666

67-
. Apply the isolated and reserved CPUs in the `PerformanceProfile` YAML. For example, you could set logical cores CPU0 and CPU4 as `isolated`, and logical cores CPU1 and CPU5 as `reserved`. When you configure reserved and isolated CPUs, the infra containers in pods use the reserved CPUs and the application containers use the isolated CPUs.
67+
. Apply the isolated and reserved CPUs in the `PerformanceProfile` YAML. For example, you can set logical cores CPU0 and CPU4 as `isolated`, and logical cores CPU1 to CPU3 and CPU5 to CPU7 as `reserved`. When you configure reserved and isolated CPUs, the infra containers in pods use the reserved CPUs and the application containers use the isolated CPUs.
6868
+
6969
[source,yaml]
7070
----
7171
...
7272
cpu:
73-
isolated: 0-4
74-
reserved: 1-5
73+
isolated: 0,4
74+
reserved: 1-3,5-7
7575
...
7676
----
77+
+
78+
[NOTE]
79+
====
80+
The reserved and isolated CPU pools must not overlap and together must span all available cores in the worker node.
81+
====
7782

7883
[IMPORTANT]
7984
====

0 commit comments

Comments
 (0)