From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E3AB6A0093 for ; Mon, 2 May 2022 13:36:22 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6D4B940F35; Mon, 2 May 2022 13:36:22 +0200 (CEST) Received: from mail.deltatec.be (mail.deltatec.be [91.183.90.4]) by mails.dpdk.org (Postfix) with ESMTP id 1C87140E28 for ; Mon, 2 May 2022 13:36:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=deltacast.tv; s=AnsUTM; h=MIME-Version:Content-Type:In-Reply-To:References: Message-ID:Date:Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ORwVREJVDDdiE5+8K6KFfkMUz3b3Ex2u82qsNWgbh3U=; b=RQd9JFlMV3bV1wjbaDid+pySls o+f8omgQgLU1/z0w9Ge3KWrdid/yWygRYChta5s0CbfpqM6bNTBQpA/zjaUvpCkUcLyXgMXNNlqdS WELX7eBzj7sjKA1DEnF1KKnCJCaqCk6A8kC60oYlWcGXQ7xyeiVrBPe2ALFc3hYfoKBo=; Received: from [172.16.4.5] (port=34797 helo=W2K19-SVR-5.office.deltatec.net) by mail.deltatec.be with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nlULa-0005op-1U; Mon, 02 May 2022 13:36:10 +0200 Received: from W2K19-SVR-5.office.deltatec.net (172.16.4.5) by W2K19-SVR-5.office.deltatec.net (172.16.4.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.3; Mon, 2 May 2022 13:36:10 +0200 Received: from W2K19-SVR-5.office.deltatec.net ([::1]) by W2K19-SVR-5.office.deltatec.net ([::1]) with mapi id 15.02.0792.003; Mon, 2 May 2022 13:36:10 +0200 From: Antoine POLLENUS To: Asaf Penso , "users@dpdk.org" , "Slava Ovsiienko" Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK Thread-Topic: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK Thread-Index: Adha+ubo+jhuqNZDTei2Is/gBt8y8QC/2VXQAAHbviAAAVrRtAAEW18Q Date: Mon, 2 May 2022 11:36:10 +0000 Message-ID: References: <686a7825fb9d4e3e8516b3d3600756ac@deltacast.tv> In-Reply-To: Accept-Language: en-US, fr-BE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.6.199] Content-Type: multipart/alternative; boundary="_000_ad63b6ff9c584dbdbe8671e78cda8184deltacasttv_" MIME-Version: 1.0 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --_000_ad63b6ff9c584dbdbe8671e78cda8184deltacasttv_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm not really familiar with testpmd, how am I supposed to do that ? From: Asaf Penso [mailto:asafp@nvidia.com] Sent: lundi 2 mai 2022 11:30 To: Antoine POLLENUS ; users@dpdk.org; Slava Ovsii= enko 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 co= mmand line. Regards, Asaf Penso ________________________________ From: Antoine POLLENUS > Sent: Monday, May 2, 2022 11:53:18 AM To: Asaf Penso >; users@dpdk.org<= mailto:users@dpdk.org> >; Slava Ovsii= enko > 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@nvidia.com] Sent: lundi 2 mai 2022 09:59 To: Antoine POLLENUS >; users@dpdk.org; Slava Ovsiienko > 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 in case you need= further support. Regards, Asaf Penso From: Antoine POLLENUS > 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 adapt= er. 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=3D0x1 --nb-cores=3D1 --eth= -peer=3D0,01:00:5e:00:00:08 --tx-ip=3D10.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 e= nabled dynf =3D rte_mbuf_dynflag_lookup (RTE_MBUF_DYNFLAG_TX_TIMESTAMP_NAME, NULL); if (dynf >=3D 0) timestamp_mask =3D 1ULL << dynf; dynf =3D rte_mbuf_dynfield_lookup (RTE_MBUF_DYNFIELD_TIMESTAMP_NAME, NULL); if (dynf >=3D 0) timestamp_off =3D dynf; both function ( rte_mbuf_dynfield_lookup and rte_mbuf_dynflag_lookup) retur= ns -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 capabilit= ies Hope you will be able to help me. Regards Antoine --_000_ad63b6ff9c584dbdbe8671e78cda8184deltacasttv_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m not really familiar with testpmd, how am I supposed to do th= at ?

 

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

 

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

 

Regards,

Asaf Penso

From: Antoine POLLENUS <a.pollenus@deltacast.tv>
Sent: Monday, May 2, 2022 11:53:18 AM
To: Asaf Penso <asafp@nvidia.= com>; users@dpdk.org <users@dpdk.org= >; Slava Ovsiienko <viaches= lavo@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@nvidia.com]
Sent: lundi 2 mai 2022 09:59
To: Antoine POLLENUS <= a.pollenus@deltacast.tv>; users@dpdk.org; Slava Ovsiienko <<= a href=3D"mailto:viacheslavo@nvidia.com">viacheslavo@nvidia.com>
Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK=

 

H= ello Antoine,

&= nbsp;

H= ave you had a look into mlx5 documentation?

<= a href=3D"http://doc.dpdk.org/guides/nics/mlx5.html">http://doc.dpdk.org/gu= ides/nics/mlx5.html

P= lease look for tx_pp.

&= nbsp;

I= ’m adding @Slava Ovsiienko in case yo= u need further support.

&= nbsp;

R= egards,

A= saf Penso

&= nbsp;

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

&= nbsp;

Hello,

 

DPDK Version: 21.11

Firmware version : 22.32.1010

MLNX_OFED version: MLNX_OFED_LINUX-5.5-1.0.3.2-ubuntu2= 0.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 wor= king.

 

The test is using Test-pmd in txonly mode.=

 

Here are the command used:

 

sudo ./dpdk-testpmd -l 0-3 -n 4 -- -i --portmask=3D0x1= --nb-cores=3D1 --eth-peer=3D0,01:00:5e:00:00:08 --tx-ip=3D10.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 missi= ng something ?

 

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

 

dynf =3D rte_mbuf_dynflag_lookup

(RTE_MBUF_DYNFLAG_TX_TIMESTAMP_NAME, NULL);

if (dynf >=3D 0)

timestamp_mask =3D 1ULL << dynf;

dynf =3D rte_mbuf_dynfield_lookup

(RTE_MBUF_DYNFIELD_TIMESTAMP_NAME, NULL);<= /o:p>

if (dynf >=3D 0)

timestamp_off =3D 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 th= ese offload capabilities

 

Hope you will be able to help me.

 

Regards

 

Antoine

--_000_ad63b6ff9c584dbdbe8671e78cda8184deltacasttv_--