[dpdk-dev] [PATCH v2 0/7] ethdev: add min/max MTU to device info

Ferruh Yigit ferruh.yigit at intel.com
Thu Mar 28 17:43:37 CET 2019


On 3/22/2019 1:01 PM, Ian Stokes wrote:
> Building upon the discussion around [1], this series introduces MTU min
> and MTU max variables. It also provides updates to PMD implementations
> for ixgbe, i40e and IGB devices so that these variables are populated
> for use when retrieving device info.
> 
> This series was tested with OVS DPDK and functions as expected for the
> drivers listed below. But a wider selection of PMD drivers would have to
> adopt this to ensure jumbo frames functionality remains for drivers not
> modified in the series.
> 
> There is also ongoing discussion in [2] regarding overhead to be
> considered with MTU and how this may change from device to device, this
> series uses existing overhead assumptions.
> 
> This series was previously posted as an RFC in [3] and a v1 in [4],
> this revision implements changes received in feedback on v1.
> 
> [1] http://mails.dpdk.org/archives/dev/2018-September/110959.html
> [2] http://mails.dpdk.org/archives/dev/2019-February/124457.html
> [3] http://mails.dpdk.org/archives/dev/2019-February/124938.html
> [4] http://mails.dpdk.org/archives/dev/2019-February/125319.html
> 
> Ian Stokes (6):
>   net/i40e: set min and max MTU for i40e devices
>   net/i40e: set min and max MTU for i40e VF devices
>   net/ixgbe: set min and max MTU for ixgbe devices
>   net/ixgbe: set min and max MTU for ixgbe VF devices
>   net/e1000: set min and max MTU for igb devices
>   app/testpmd: verify mtu with rte_eth_dev_info_get()
> 
> Stephen Hemminger (1):
>   ethdev: add min/max MTU to device info

Final notice about the patch, if there is no objection will be merged tomorrow
this for rc1.

Reminder that all net PMD maintainers should update according this new 'min_mtu'
& 'max_mtu' approach.


More information about the dev mailing list