1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/cnf-use-device-interrupt-processing-for-isolated-cpus.adoc
Aidan Reilly d51917ed74 low latency tuning refactor
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
2024-05-10 09:01:21 +00:00

33 lines
1.9 KiB
Plaintext

// Module included in the following assemblies:
//
// * scalability_and_performance/low_latency_tuning/cnf-provisioning-low-latency-workloads.adoc
// * scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.adoc
[id="nto_supported_api_versions_{context}"]
= Supported performance profile API versions
The Node Tuning Operator supports `v2`, `v1`, and `v1alpha1` for the performance profile `apiVersion` field. The v1 and v1alpha1 APIs are identical. The v2 API includes an optional boolean field `globallyDisableIrqLoadBalancing` with a default value of `false`.
[discrete]
[id="use-device-interrupt-processing-for-isolated-cpus_{context}"]
== Upgrading the performance profile to use device interrupt processing
When you upgrade the Node Tuning Operator performance profile custom resource definition (CRD) from v1 or v1alpha1 to v2, `globallyDisableIrqLoadBalancing` is set to `true` on existing profiles.
[NOTE]
====
`globallyDisableIrqLoadBalancing` toggles whether IRQ load balancing will be disabled for the Isolated CPU set. When the option is set to `true` it disables IRQ load balancing for the Isolated CPU set. Setting the option to `false` allows the IRQs to be balanced across all CPUs.
====
[discrete]
[id="upgrading_nto_api_from_v1alpha1_to_v1_{context}"]
=== Upgrading Node Tuning Operator API from v1alpha1 to v1
When upgrading Node Tuning Operator API version from v1alpha1 to v1, the v1alpha1 performance profiles are converted on-the-fly using a "None" Conversion strategy and served to the Node Tuning Operator with API version v1.
[discrete]
[id="upgrading_nto_api_from_v1alpha1_to_v1_or_v2_{context}"]
=== Upgrading Node Tuning Operator API from v1alpha1 or v1 to v2
When upgrading from an older Node Tuning Operator API version, the existing v1 and v1alpha1 performance profiles are converted using a conversion webhook that injects the `globallyDisableIrqLoadBalancing` field with a value of `true`.