Hi Mark,
Mark Kavanagh <[email protected]> writes:
> DPDK provides an API to set the MTU of compatible physical devices -
> rte_eth_dev_set_mtu(). Prior to DPDK v16.07 however, this API was not
> implemented in some DPDK PMDs (i40e, specifically). To allow the use
> of jumbo frames with affected NICs in OvS-DPDK, MTU configuration was
> achieved by setting the jumbo frame flag, and corresponding maximum
> permitted Rx frame size, in an rte_eth_conf structure for the NIC
> port, and subsequently invoking rte_eth_dev_configure() with that
> configuration.
>
> However, that method does not set the MTU field of the underlying DPDK
> structure (rte_eth_dev) for the corresponding physical device;
> consequently, rte_eth_dev_get_mtu() reports the incorrect MTU for an
> OvS-DPDK phy device with non-standard MTU.
>
> Resolve this issue by invoking rte_eth_dev_set_mtu() when setting up
> or modifying the MTU of a DPDK phy port.
>
> Fixes: 0072e93 ("netdev-dpdk: add support for jumbo frames")
> Reported-by: Vipin Varghese <[email protected]>
> Signed-off-by: Mark Kavanagh <[email protected]>
> ---
I think I should also get a reported-by tag for this ;) :
https://mail.openvswitch.org/pipermail/ovs-dev/2016-January/308828.html
I should have probably not claimed that it wasn't a show-stopper. I
also don't see the comment I requested you to add that would warn us to
revisit this in the future :(
I will carve out some time to apply and test this. Thanks Mark.
-Aaron
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
