[dpdk-dev] [PATCH v2 0/4] ethdev: add per-PMD tuning of RxTx parmeters
Ferruh Yigit
ferruh.yigit at intel.com
Tue Mar 27 20:43:10 CEST 2018
On 3/21/2018 2:27 PM, Remy Horton wrote:
> The optimal values of several transmission & reception related parameters,
> such as burst sizes, descriptor ring sizes, and number of queues, varies
> between different network interface devices. This patchset allows individual
> PMDs to specify their preferred parameter values, and if so indicated by an
> application, for them to be used automatically by the ethdev layer.
>
> rte_eth_dev_configure() has been changed so that specifying zero for both
> nb_rx_q AND nb_tx_q causes it to use driver preferred values, and if these
> are not available, falls back to EAL defaults. Setting one (but not both)
> to zero does not cause the use of defaults, as having one of them zeroed is
> a valid setup.
>
> This RFC/V1 includes per-PMD values for e1000 and i40e but it is expected
> that subsequent patchsets will cover other PMDs. A deprecation notice
> covering the API/ABI change is in place.
>
>
> Changes in v2:
> * Rebased to
> * Removed fallback values from rte_eth_dev_info_get()
> * Added fallback values to rte_rte_[rt]x_queue_setup()
> * Added fallback values to rte_eth_dev_configure()
> * Corrected comment
> * Removed deprecation notice
> * Split RX and Tx into seperate structures
> * Changed parameter names
>
>
> Remy Horton (4):
> ethdev: add support for PMD-tuned Tx/Rx parameters
> net/e1000: add TxRx tuning parameters
> net/i40e: add TxRx tuning parameters
> testpmd: make use of per-PMD TxRx parameters
Reviewed-by: Ferruh Yigit <ferruh.yigit at intel.com>
More information about the dev
mailing list