Description of problem:
TripleO support for Jumbo frames and Multiqueue
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Blueprint Details below.
The feature “Jumbo Frames” can be enabled by configuring the MTU value for the OVS-DPDK interface and OVS-DPDK bond. Already os-net-config supports an option for providing MTU values, but for DPDK it has to be set to the OvS DB with below command:
ovs-vsctl -- set Interface <DPDK device> mtu_request=<frame size>
DPDK port types in os-net-config shall append this to ovs_extra and update to the ifcfg files if MTU value is set on the DPDK interface and bond.
OVS2.6 has support to specify the number of multi-queues per physical interface. The command, “ovs-vsctl set Interface <DPDK interface> options:n_rxq=<integer>”, will set the number of multi-queues in OvS DB, that can be used for this interface. The rx queues are assigned to pmd threads on the same NUMA node in a round-robin fashion.
A new parameter “rx_queues” shall be added to all DPDK interface types to configure the number of queues.
- type: ovs_user_bridge
Note that this value can be provided via ovs_extra of the interface, but having it as separate value provides better usability.
Has been verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.