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 1B605A034C for ; Thu, 28 Apr 2022 14:25:16 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A024242819; Thu, 28 Apr 2022 14:25:15 +0200 (CEST) Received: from mail.deltatec.be (mail.deltatec.be [91.183.90.4]) by mails.dpdk.org (Postfix) with ESMTP id 807DB40E50 for ; Thu, 28 Apr 2022 14:25:14 +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: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:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=9f0rLMnN+ySehpaWUkyj5g3MlN4yaJr2EeC3EQf9L70=; b=sX3T2fBN+FSvtguOKiU9pSCoa4 QTnaujrmI3Tz7wMO235MLEGFDqn8WIcZpxSpBy2j9S6vxUdIA493xewGBJdzyA+RVLdPRsTWRud6D CAh0HZlTqOEKioMHwnCOPfw/ThFAevcBd5IkErs3SQnLVISw4Elu7Sc5jvGtxeXFLH9U=; Received: from [172.16.4.5] (port=11910 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 1nk3Cp-0002zB-05 for users@dpdk.org; Thu, 28 Apr 2022 14:25:11 +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; Thu, 28 Apr 2022 14:25: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; Thu, 28 Apr 2022 14:25:10 +0200 X-SASI-Hits: BODYTEXTH_SIZE_10000_LESS 0.000000, BODYTEXTH_SIZE_3000_MORE 0.000000, BODYTEXTP_SIZE_3000_LESS 0.000000, HTML_70_90 0.100000, LINES_OF_YELLING_3 0.050000, NO_CTA_FOUND 0.000000, NO_CTA_URI_FOUND 0.000000, NO_FUR_HEADER 0.000000, NO_URI_HTTPS 0.000000, OBFU_SHORT_10CHARS 0.500000, OUTBOUND 0.000000, OUTBOUND_SOPHOS 0.000000, SENDER_NO_AUTH 0.000000, WEBMAIL_SOURCE 0.000000, WEBMAIL_XOIP 0.000000, WEBMAIL_X_IP_HDR 0.000000, __ANY_URI 0.000000, __BODY_NO_MAILTO 0.000000, __BODY_TEXT_X4 0.000000, __BULK_NEGATE 0.000000, __CT 0.000000, __CTYPE_HAS_BOUNDARY 0.000000, __CTYPE_MULTIPART 0.000000, __CTYPE_MULTIPART_ALT 0.000000, __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000, __FROM_DOMAIN_NOT_IN_BODY 0.000000, __FROM_NAME_NOT_IN_BODY 0.000000, __FUR_RDNS_SOPHOS 0.000000, __HAS_FROM 0.000000, __HAS_HTML 0.000000, __HAS_MSGID 0.000000, __HAS_XOIP 0.000000, __HTML_TAG_DIV 0.000000, __LINES_OF_YELLING 0.000000, __MIME_HTML 0.000000, __MIME_TEXT_H 0.000000, __MIME_TEXT_H1 0.000000, __MIME_TEXT_H2 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_TEXT_P2 0.000000, __MIME_VERSION 0.000000, __MSGID_32HEX 0.000000, __OUTBOUND_SOPHOS_FUR 0.000000, __OUTBOUND_SOPHOS_FUR_IP 0.000000, __OUTBOUND_SOPHOS_FUR_RDNS 0.000000, __PHISH_SPEAR_SUBJ_ALERT 0.000000, __SANE_MSGID 0.000000, __STYLE_RATWARE_NEG 0.000000, __STYLE_TAG 0.000000, __SUBJ_ALPHA_END 0.000000, __SUBJ_STARTS_S_BRACKETS 0.000000, __TAG_EXISTS_HTML 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NO_NAME 0.000000, __URI_NO_MAILTO 0.000000, __URI_NO_WWW 0.000000 X-SASI-Probability: 10% X-SASI-RCODE: 200 X-SASI-Version: Antispam-Engine: 4.1.4, AntispamData: 2022.4.28.115419 From: Antoine POLLENUS To: "users@dpdk.org" Subject: [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/gBt8y8Q== Date: Thu, 28 Apr 2022 12:25:10 +0000 Message-ID: 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_fa52141d87334ce5a547779740a9948edeltacasttv_" 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_fa52141d87334ce5a547779740a9948edeltacasttv_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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_fa52141d87334ce5a547779740a9948edeltacasttv_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

&nbs= p;

DPDK Vers= ion: 21.11

Firmware = version : 22.32.1010

MLNX_OFED= version: MLNX_OFED_LINUX-5.5-1.0.3.2-ubuntu20.04-x86_64<= /p>

&nbs= p;

We are tr= ying to use the DPDK tx scheduling feature on a ConnectX6 DX adapter. We ex= perience some issues with the feature not working.

&nbs= p;

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

&nbs= p;

Here are = the command used:

&nbs= p;

sudo ./dp= dk-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&g= t; set fwd txonly

testpmd&g= t; set burst 64

testpmd&g= t; set txtimes 1000000,10000

&nbs= p;

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

&nbs= p;

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

&nbs= p;

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;

&nbs= p;

both func= tion ( rte_mbuf_dynfield_lookup and rte_mbuf_dynflag_lookup) returns -1

&nbs= p;

I also tr= ied to enabled the feature.

&nbs= p;

testpmd&g= t; port config 0 tx_offload send_on_timestamp on

but when = doing this DPDK tells me that I don't have these offload capabilities<= /o:p>

&nbs= p;

Hope you = will be able to help me.

&nbs= p;

Regards

 =

Antoine

--_000_fa52141d87334ce5a547779740a9948edeltacasttv_--