[ConnectX 6Dx]Issue using Tx scheduling feature in DPDK

[Asaf Penso]

Example:


dpdk-testpmd -c 0x7ffc0000 -n 4 -a d8:00.1, tx_pp=1 -a d8:00.0,tx_pp=1--burst=64 --txd=256 --rxd=256 --mbcache=512 --rxq=2 --txq=2 --nb-cores=1 --no-lsc-interrupt -i --auto-start --rss-udp

You can read more about testpmd and the specific mlx5 devargs for tx_pp here:
http://doc.dpdk.org/guides/nics/mlx5.html

Regards,
Asaf Penso
________________________________
From: Antoine POLLENUS <a.pollenus at deltacast.tv>
Sent: Monday, May 2, 2022 2:36:10 PM
To: Asaf Penso <asafp at nvidia.com>; users at dpdk.org <users at dpdk.org>; Slava Ovsiienko <viacheslavo at nvidia.com>
Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK


I’m not really familiar with testpmd, how am I supposed to do that ?



From: Asaf Penso [mailto:asafp at nvidia.com]
Sent: lundi 2 mai 2022 11:30
To: Antoine POLLENUS <a.pollenus at deltacast.tv>; users at dpdk.org; Slava Ovsiienko <viacheslavo at nvidia.com>
Subject: Re: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK



For example, I don't see you add the tx_pp devarg as part of the testpmd command line.



Regards,

Asaf Penso

________________________________

From: Antoine POLLENUS <a.pollenus at deltacast.tv<mailto:a.pollenus at deltacast.tv>>
Sent: Monday, May 2, 2022 11:53:18 AM
To: Asaf Penso <asafp at nvidia.com<mailto:asafp at nvidia.com>>; users at dpdk.org<mailto:users at dpdk.org> <users at dpdk.org<mailto:users at dpdk.org>>; Slava Ovsiienko <viacheslavo at nvidia.com<mailto:viacheslavo at nvidia.com>>
Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK



Thanks for you answer,

Already red the doc on the subject but can’t make it work in testpmd.
Didn’t implemented it myself at this step but seams I’m missing something.

Do I need to enable a specific offload ?



From: Asaf Penso [mailto:asafp at nvidia.com]
Sent: lundi 2 mai 2022 09:59
To: Antoine POLLENUS <a.pollenus at deltacast.tv<mailto:a.pollenus at deltacast.tv>>; users at dpdk.org<mailto:users at dpdk.org>; Slava Ovsiienko <viacheslavo at nvidia.com<mailto:viacheslavo at nvidia.com>>
Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK



Hello Antoine,



Have you had a look into mlx5 documentation?

http://doc.dpdk.org/guides/nics/mlx5.html

Please look for tx_pp.



I’m adding @Slava Ovsiienko<mailto:viacheslavo at nvidia.com> in case you need further support.



Regards,

Asaf Penso



From: Antoine POLLENUS <a.pollenus at deltacast.tv<mailto:a.pollenus at deltacast.tv>>
Sent: Thursday, April 28, 2022 3:25 PM
To: users at dpdk.org<mailto:users at dpdk.org>
Subject: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK



Hello,



DPDK Version: 21.11

Firmware version : 22.32.1010

MLNX_OFED version: MLNX_OFED_LINUX-5.5-1.0.3.2-ubuntu20.04-x86_64



We are trying to use the DPDK tx scheduling feature on a ConnectX6 DX adapter. We experience some issues with the feature not working.



The test is using Test-pmd in txonly mode.



Here are the command used:



sudo ./dpdk-testpmd -l 0-3 -n 4 -- -i --portmask=0x1 --nb-cores=1 --eth-peer=0,01:00:5e:00:00:08 --tx-ip=10.10.1.168,239.0.0.8

testpmd> set fwd txonly

testpmd> set burst 64

testpmd> set txtimes 1000000,10000



By doing this I expect the feature working. Am i missing something ?



I also added a print in txonly.c and clearly sees that the feature is not enabled



dynf = rte_mbuf_dynflag_lookup

(RTE_MBUF_DYNFLAG_TX_TIMESTAMP_NAME, NULL);

if (dynf >= 0)

timestamp_mask = 1ULL << dynf;

dynf = rte_mbuf_dynfield_lookup

(RTE_MBUF_DYNFIELD_TIMESTAMP_NAME, NULL);

if (dynf >= 0)

timestamp_off = dynf;



both function ( rte_mbuf_dynfield_lookup and rte_mbuf_dynflag_lookup) returns -1



I also tried to enabled the feature.



testpmd> port config 0 tx_offload send_on_timestamp on

but when doing this DPDK tells me that I don't have these offload capabilities



Hope you will be able to help me.



Regards



Antoine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/users/attachments/20220519/48669c3e/attachment-0001.htm>