mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
d51917ed74
Changes for Martin Martin's 3rd review comments Martin's 4th review Final comments from Martin More updates for Martin Tweaks for Martin Martin's comments 22-Apr - workload pods Apr 30 review comments final review comments Michael's comments
42 lines
1.6 KiB
Plaintext
42 lines
1.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="configuring_for_irq_dynamic_load_balancing_{context}"]
|
|
= Configuring node interrupt affinity
|
|
|
|
Configure a cluster node for IRQ dynamic load balancing to control which cores can receive device interrupt requests (IRQ).
|
|
|
|
.Prerequisites
|
|
|
|
* For core isolation, all server hardware components must support IRQ affinity. To check if the hardware components of your server support IRQ affinity, view the server's hardware specifications or contact your hardware provider.
|
|
|
|
.Procedure
|
|
|
|
. Log in to the {product-title} cluster as a user with cluster-admin privileges.
|
|
. Set the performance profile `apiVersion` to use `performance.openshift.io/v2`.
|
|
. Remove the `globallyDisableIrqLoadBalancing` field or set it to `false`.
|
|
. Set the appropriate isolated and reserved CPUs. The following snippet illustrates a profile that reserves 2 CPUs. IRQ load-balancing is enabled for pods running on the `isolated` CPU set:
|
|
+
|
|
[source,yaml]
|
|
----
|
|
apiVersion: performance.openshift.io/v2
|
|
kind: PerformanceProfile
|
|
metadata:
|
|
name: dynamic-irq-profile
|
|
spec:
|
|
cpu:
|
|
isolated: 2-5
|
|
reserved: 0-1
|
|
...
|
|
----
|
|
+
|
|
[NOTE]
|
|
====
|
|
When you configure reserved and isolated CPUs, operating system processes, kernel processes, and systemd services run on reserved CPUs.
|
|
Infrastructure pods run on any CPU except where the low latency workload is running.
|
|
Low latency workload pods run on exclusive CPUs from the isolated pool.
|
|
For more information, see "Restricting CPUs for infra and application containers".
|
|
====
|