From: Asaf Penso <asafp@nvidia.com>
To: Antoine POLLENUS <a.pollenus@deltacast.tv>,
"users@dpdk.org" <users@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK
Date: Mon, 2 May 2022 07:58:54 +0000 [thread overview]
Message-ID: <DM5PR1201MB2555DD6142B6C3C393192536CDC19@DM5PR1201MB2555.namprd12.prod.outlook.com> (raw)
In-Reply-To: <fa52141d87334ce5a547779740a9948e@deltacast.tv>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
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@nvidia.com> in case you need further support.
Regards,
Asaf Penso
From: Antoine POLLENUS <a.pollenus@deltacast.tv>
Sent: Thursday, April 28, 2022 3:25 PM
To: users@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
[-- Attachment #2: Type: text/html, Size: 7311 bytes --]
next prev parent reply other threads:[~2022-05-02 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 12:25 Antoine POLLENUS
2022-05-02 7:58 ` Asaf Penso [this message]
2022-05-02 8:53 ` Antoine POLLENUS
2022-05-02 9:30 ` Asaf Penso
2022-05-02 11:36 ` Antoine POLLENUS
2022-05-19 4:39 ` Asaf Penso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM5PR1201MB2555DD6142B6C3C393192536CDC19@DM5PR1201MB2555.namprd12.prod.outlook.com \
--to=asafp@nvidia.com \
--cc=a.pollenus@deltacast.tv \
--cc=users@dpdk.org \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).