You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/k8s-best-practices-cpu-manager-pinning.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
[id="k8s-best-practices-cpu-manager-pinning"]
2
2
= CPU manager/pinning
3
3
4
-
The OpenShift platform can use the Kubernetes CPU Manager to support allocation of cores using kubernetes guaranteed QoS class for applications. Isolcpus is not enabled.
4
+
The OpenShift platform can use the Kubernetes CPU Manager to support allocation of cores using kubernetes guaranteed QoS class for applications. Isolcpus is not enabled.
5
5
6
6
Important note on using probes: If the workload is doing CPU pinning and running a DPDK process do
7
7
not use exec probes (executing a command within the container) as it may pile up and block the
0 commit comments