Loading...

XML

Word

Printable

Acceptance Criteria:
Hide

Given a DPDK bond (e.g., dpdkbond1) with MTU 9200 and member ports (e.g., dpdk2, dpdk3),

When the bond’s MTU is configured via NetworkManager,

Then, the mtu_request of each member DPDK port is automatically set to 9200 and the OVS command set Interface $PORT mtu_request=9200 is executed for all bond members.

Definition of Done

NetworkManager’s OVS plugin supports mtu_request configuration.

Integration tests validate polling mode and MTU propagation.

Code is part of a downstream build attached to an errata and backported to RHEL 9.4.

Documentation updated for new OVS-DPDK options.
Show
Given a DPDK bond (e.g., dpdkbond1) with MTU 9200 and member ports (e.g., dpdk2, dpdk3), When the bond’s MTU is configured via NetworkManager, Then, the mtu_request of each member DPDK port is automatically set to 9200 and the OVS command set Interface $PORT mtu_request=9200 is executed for all bond members. Definition of Done NetworkManager’s OVS plugin supports mtu_request configuration. Integration tests validate polling mode and MTU propagation. Code is part of a downstream build attached to an errata and backported to RHEL 9.4. Documentation updated for new OVS-DPDK options.
Preliminary Testing:
None
Test Coverage:
None

We need to enable NetworkManager’s OVS plugin to configure dpdk-lsc-interrupt=false and propagate mtu_request to DPDK physical ports in a bond.

These settings are important for RHOSP NFV/telco customers using OVS-DPDK with polling mode drivers to achieve maximum performance.

This ticket is related to RHEL-53956.

clones

RHEL-77148 [RFE] NetworkManager: Support OVS-DPDK dpdk-lsc-interrupt configuration