Add --ovs-dpdk-cpu-count flag to PPC documentation - #119735
Conversation
Updated Performance Profile Creator documentation to include the new --ovs-dpdk-cpu-count flag that was added in OpenShift 5.0. This flag allows users to specify the number of CPUs to reserve for OVS-DPDK PMD threads, which populates spec.cpu.ovsDpdk in the generated performance profile. Changes: - Added ovs-dpdk-cpu-count to optional arguments reference table - Included description of CPU allocation behavior (after reserved/offlined) - Added IMPORTANT note about NUMA locality verification requirement - Updated help output in both Podman and offline PPC modules - Documented default value of 0 (no OVS-DPDK CPUs reserved) Related to upstream PR: openshift/cluster-node-tuning-operator#1630 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
🤖 Mon Sep 14 11:09:06 - Prow CI generated the docs preview: |
- Add spec.cpu.ovsDpdk field to YAML template - Add reference to Performance Profile Creator with --ovs-dpdk-cpu-count - Add guidance on NUMA placement for OVS-DPDK CPUs Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
- Add link to "Reserving CPUs for OVS-DPDK" documentation Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
Error on preview building valid as PR #116259 not merged yet |
|
|
||
| * link:https://access.redhat.com/articles/7081587[Understanding workload hints] | ||
|
|
||
| * * xref:../scalability_and_performance/cnf-reserving-cpus-for-ovs-dpdk.adoc#cnf-reserving-cpus-for-ovs-dpdk[Reserving CPUs for OVS-DPDK] |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.RelatedLinks: Content other than links cannot be mapped to DITA related-links.
|
@kquinn1204: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Tal-or
left a comment
There was a problem hiding this comment.
LGTM but I see CI is failing.
Please fix the issues first and i'll apporve
Updated Performance Profile Creator documentation to include the new --ovs-dpdk-cpu-count flag that was added in OpenShift 5.0.
This flag allows users to specify the number of CPUs to reserve for OVS-DPDK PMD threads, which populates spec.cpu.ovsDpdk in the generated performance profile.
Changes:
Related to upstream PR: openshift/cluster-node-tuning-operator#1630
Version(s):
Issue:
Link to docs preview:https://119735--ocpdocs-pr.netlify.app/openshift-enterprise/latest/scalability_and_performance/cnf-tuning-low-latency-nodes-with-perf-profile.html
QE review:
Additional information: