CNF-23565: Dedicate CPU resources for DPDK-based vSwitch/vRouter#2001
CNF-23565: Dedicate CPU resources for DPDK-based vSwitch/vRouter#2001Tal-or wants to merge 2 commits into
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@Tal-or: This pull request references CNF-23565 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
…Router Adds enhancement proposal for dedicating CPUs exclusively for infrastructure networking workloads (OVS-DPDK, OpenPErouter). Introduces two new PerformanceProfile API fields: spec.cpu.dedicated and spec.net.disableOvsDynamicPinning. Tracking: CNF-22582, RFE-8921 AIA Human-AI blend, New content, Human-initiated, Reviewed, Claude Opus 4.6 v1.0 Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Tal-or
force-pushed
the
dedicate_cpus_for_dpdk_vswitch
branch
from
192566c to
c941e7f
Compare
jmencak
left a comment
jmencak
left a comment
There was a problem hiding this comment.
Looks good to me overall. Have a couple of questions to improve my understanding of the problem and found a few nits.
|
|
||
| ### Non-Goals | ||
|
|
||
| - Managing the lifecycle of OVS-DPDK processes themselves (PMD thread creation, DPDK EAL |
There was a problem hiding this comment.
I understand this is a non-goal, however, I'd like to understand how the OVS-DPDK processes run in OpenShift. So, they're not managed by kubelet at all? Do they run as regular userspace processes outside of OpenShift control?
There was a problem hiding this comment.
So, they're not managed by kubelet at all?
They are not.
Do they run as regular userspace processes outside of OpenShift control?
AFAIU, yes.
The user will by pass the kernel networking stack and all infra-communication will be done through the DPDK talking directly to the NICs
I believe @MarSik can add more details and clarity about that
Tal-or
force-pushed
the
dedicate_cpus_for_dpdk_vswitch
branch
5 times, most recently
from
9342e11 to
60e437d
Compare
Add on different commit for clarity. Will squash once it'll be ready to merge. Signed-off-by: Talor Itzhak <titzhak@redhat.com>
Tal-or
force-pushed
the
dedicate_cpus_for_dpdk_vswitch
branch
from
60e437d to
b632c5c
Compare
|
@Tal-or: all tests passed! 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. |
4 participants
Adds enhancement proposal for dedicating CPUs exclusively for infrastructure networking workloads (OVS-DPDK, OpenPErouter). Introduces two new PerformanceProfile API fields: spec.cpu.dedicated and spec.net.disableOvsDynamicPinning.
Tracking: CNF-22582, RFE-8921
AIA Human-AI blend, New content, Human-initiated, Reviewed, Claude Opus 4.6 v1.0
Signed-off-by: Talor Itzhak titzhak@redhat.com