[dpdk-dev] [PATCH v2] app/testpmd: configure rxd and txd number correctly

Ferruh Yigit ferruh.yigit at intel.com
Tue Apr 21 19:24:50 CEST 2020


On 4/21/2020 12:50 PM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: dev <dev-bounces at dpdk.org> On Behalf Of Lijun Ou
>> Sent: Saturday, April 18, 2020 4:45 AM
>> To: Ye, Xiaolong <xiaolong.ye at intel.com>; Zhang, Qi Z
>> <qi.z.zhang at intel.com>
>> Cc: dev at dpdk.org; linuxarm at huawei.com
>> Subject: [dpdk-dev] [PATCH v2] app/testpmd: configure rxd and txd number
>> correctly
>>
>> When users configure rxds and txds by used port config cmd based on
>> testpmd application, it will not be able to configure rxd and txd according to
>> the max capability range supported by the actual NIC hardware. Due testpmd
>> defects, it can only configure a fixed range to 0 to 2048.
>> The final result is that an incorrect printing prompt appears and cannot be
>> applied using rxd && txd according to the actual capabilities supported by the
>> device.
>> In order to solve the above problems, we modify the testpmd. First by calling
>> the rte_eth_dev_info_get api to obtain the max and min rx/tx capability
>> supported by the hns3, and then use this range to compare with the actual
>> value by users configured and make reasonable limitation.
>>
>> Signed-off-by: Lijun Ou <oulijun at huawei.com>
>> Signed-off-by: Huisong Li <lihuisong at huawei.com>
>> Signed-off-by: Wei Hu (Xavier) <xavier.huwei at huawei.com>
> 
> Acked-by: Bernard Iremonger <bernard.iremonger at intel.com>
> 

Applied to dpdk-next-net/master, thanks.


More information about the dev mailing list