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 C3055A0093 for ; Mon, 2 May 2022 11:30:19 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4E72F40F35; Mon, 2 May 2022 11:30:19 +0200 (CEST) Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2066.outbound.protection.outlook.com [40.107.236.66]) by mails.dpdk.org (Postfix) with ESMTP id E836640E28 for ; Mon, 2 May 2022 11:30:17 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=T5MUdGVURpnwFXzkA/FaYUdokcGDsCdjIOFXyaVUYeuVKStulR7BV3c1PIM4LkdQ5AM2v2OyW2cNWj0n/wJeRZ1kezFz6PTmD8YZt2/7D9OrxUGW9Oecwnavqg1h8nk+EE+YeLiS+U8jDlaE6PtYPdcCj/spj3wq6NEYSLRoZs+X9WAWo/v7bXBYEmUiN280EQHnKVdLbmGuSx/mwXC3J8e3RoZ5g5Qjc4HRlj+eeSgOoCieFwx/5l9vDpCZVO07ipZ7Hq1EMf5JMMVyUGEg1xkqwVIwhGwdHwka+8AM71PLqotFqwk4HXHyPuwnrmjDvg7cAPU/GoGvdQwTMNAv4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=RXnz6c7ATXzzRlHzMHRV1+8CwhZO36ctl5JtYI+WcJk=; b=SAx6vNHay6nlgQPBK9l8siF0HvgRwP3l/oAIthocffX/gDhDzKko7vrkhgXIbm4oNYa0D5kfGyXB2jUuEiwhYqc5bi8J8i8+WEh+TDuJ4GnmSgmq+x0ZkUdOgEfUCVlQ4x7xDw0FNme+0TCtdYE1BTMc9S0ZkyehaBxncMugHyGKTq4e74uo7gDf1jV4mXIdkV41IDM1nEcchm7Dxh2U5a7HcI0qgWd9zZlZxnYqnOFeYBVmtkHCoEhyTAsrzbEP57upYqrAkICg4CIho19VJApX5VWu//r4S0N+qLM7cRJ94Wa7194zW7y0Zh4lUwvKOATctLkLEHoBVetCEgq/LQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nvidia.com; dmarc=pass action=none header.from=nvidia.com; dkim=pass header.d=nvidia.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Nvidia.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RXnz6c7ATXzzRlHzMHRV1+8CwhZO36ctl5JtYI+WcJk=; b=YY8c7JhNnK+WpqIByTQTTD/ik2BsiPwJrFxO64985MT1jpKdcDfOViZoQw+buUo6KlJJoLWUzCuLwNcuu0S6b5TuGkpRcgbyJF+giDR7/3HDy6Ft/aVg2N21gPnP47WR6l2GQdvEIE1NtUze8w6jIq8vGo8+yCuKvpApf5Jai9rzy67W60bRaphVEkzeTVm1eHa2L8PSfKkhQ9jMqxh2g3X8dM9MpwiPbhAXYfzBpir3RSo2C6U7OhqvuLhwix2TZ/nnIwB/6rt04pWKgGSYAYwtyq4eyiUMJhHidqcu0LtEal43NEmBQfIJZ1KkcxOkLmodEbMic1jP7feaKUzaTA== Received: from DM5PR1201MB2555.namprd12.prod.outlook.com (2603:10b6:3:ea::14) by DM6PR12MB4498.namprd12.prod.outlook.com (2603:10b6:5:2a2::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5206.13; Mon, 2 May 2022 09:30:15 +0000 Received: from DM5PR1201MB2555.namprd12.prod.outlook.com ([fe80::fc34:2203:ac1b:bffd]) by DM5PR1201MB2555.namprd12.prod.outlook.com ([fe80::fc34:2203:ac1b:bffd%2]) with mapi id 15.20.5186.028; Mon, 2 May 2022 09:30:15 +0000 From: Asaf Penso To: Antoine POLLENUS , "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/2VXQAAHbviAAAVrRtA== Date: Mon, 2 May 2022 09:30:15 +0000 Message-ID: References: <686a7825fb9d4e3e8516b3d3600756ac@deltacast.tv> In-Reply-To: <686a7825fb9d4e3e8516b3d3600756ac@deltacast.tv> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=nvidia.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: c4009a53-0018-4661-067e-08da2c1e5d3f x-ms-traffictypediagnostic: DM6PR12MB4498:EE_ x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: WjtpluBPwiXh42CiaeXVIJYOZHWnJOMlTfWo4hBo5R6Xz+vk3vl+kKXSfSBfHJ+vn7FpEXGw5uI9g6+f5zqZw4suHItqfXY5vukknFZYuqMSdzscOHS55cyKToa1/yX/YREawXVsnWKPxnPgQIOGfQ+w+3+76cZP1xED8il8/IP8XAwI8EMEx1dso+Z+ekottFPJjkByUJrfaPw4x7+2+7LA0Ko0toTKQ1sl6L0E+KwO6iuJuQipCh20rInuKqHxLGU31mfA55BjTEXR2GyO9BpKedmGFtuecZrj9p4BZ7Y5qka30RAAuWyiwzdG2hmqnPTa3nWDthVm6BpwhE5gaw64VoZB5/JXcm+/STgZ+Xp5U12TQnkI29ZnaZNPr6DGtJFlcM8hl92wnW0mCv5rkSdoL+FkCDW2fNa6sPEDN+cBREripzlbSMfVatWia/uXbQWHzlkkngFSN+K2kQYSb9y5761NXgXL2owP858hVJXw1jwKmcaYX4BDwpA/xXAZPRmktt3ia4KbVmSYwPTKHUXxvtctuSwnqY63jUT1IljnXTZQV+StUE5urnG8VVoSCyvPszf9lJefjM9696+bplkc2CupFZp/7NvyBiA1L2h1MlkCj0X2NYZDTfjiMt48kVMnx0eUao5w/uC3yjMrxZLslGHM6t1tMcfgBJCtONuCvlBHNijyGqomuR8kGzlfF1ipF4F6jrbP4xOabRpUuPcy5F3u4+Y+p57ZVhS+svbE4EN+5IExQ+DyYPPSCXkvZux/gj4S1xIcGGzQqnTWeTe7Jb/wj8GP78J4PzPaBItyrblf+9qAqkT4a28EjSgG x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM5PR1201MB2555.namprd12.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(71200400001)(21615005)(6506007)(53546011)(7696005)(2906002)(52536014)(8936002)(186003)(966005)(26005)(508600001)(5660300002)(9686003)(86362001)(33656002)(110136005)(316002)(166002)(19627235002)(66556008)(64756008)(8676002)(66476007)(6636002)(66446008)(91956017)(76116006)(66946007)(122000001)(38070700005)(38100700002)(55016003)(562404015); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?VBh+olxEhXZus4q3Y9+bS4iZSD0Ado2/2MTT3JCpZwHTscvw0Q/B0rCY?= =?Windows-1252?Q?6JQZn4O6PUoQ1tkGemkYQ5ObTCwpCfyiocGjsyCjNLF/mTp5xdg8vX5S?= =?Windows-1252?Q?8AC7cSXS/MDP+K0iTW0eJKrCYjmCzfMXjzRcHL2HqII0sq2Fz0n4+K8C?= =?Windows-1252?Q?OSfHVCxKk1M1MfH1Ea4XJNz+22MDzFJilgXcsUAuJhTqCHon2va2RlbK?= =?Windows-1252?Q?XAs2xduUy1gP9hWOhmOei12nEsmLt71dK6IDfcVONL0cvHG+81M/laNV?= =?Windows-1252?Q?OkviLAvqY+s2y/kjPivKZyU3bEnQg4pL5JE/+DDFk+u0axLsu29YK9Ix?= =?Windows-1252?Q?b/9PYrpnIgX2cCzzRQ6Nbvb7YqoxZzdfkFO2/AwqPNNbnVtxvLhCq9sv?= =?Windows-1252?Q?tYxIln3hv4VAfzbRuxXUNbJWSyqci8BbLatz5D/N/ZpH5a4+MXPbL0Be?= =?Windows-1252?Q?B85J5LXx5lNHi9FtlNsFyhJ6kdDIZDN2BR/bJMDG/KO5Bvy1SXALImxr?= =?Windows-1252?Q?t9oBTAKNWAgwCk5CBQZREJPJzaQZXM+o+e16XOTe2tgX34+TiNaEda5+?= =?Windows-1252?Q?75thSYxzD2/IHL+fBNZDmMQn4W2M0eDi/LJt61HUs/3vVp/zzYWRGHwl?= =?Windows-1252?Q?gRLGCVHJW4GIQ7uUVbldAsKI8jw/rd1/pEWWMECifg6jK0aQz/rx18/j?= =?Windows-1252?Q?KS3oJwIRgSA7YP1ic01Jquel0Ju29FUb58Gc/8Q83o7AwY9Ciy8VCmwv?= =?Windows-1252?Q?z6lUvbRWld41YLi2NTYZDvyH9Xosf+LXdRqW8qiB4IhC+pqgXonL5uE2?= =?Windows-1252?Q?2iAODPOirAzTynmr+1tf4w19XJugJzTQ/xGDFyeGPyToiVEp+VN4Ii/S?= =?Windows-1252?Q?NGVI3IHR9yoHWZnpWd8FbtoOLDzA2uCVomX4gES62O+I8tHvww4/K+dR?= =?Windows-1252?Q?NKASIJ7BtgOBVRpBEBQ/Vd1EjqGNmezOsdaldpKNl0Gaan/gtRVzBx52?= =?Windows-1252?Q?x9VEykbowSQmzlspPouhIZY0QF95OP0wglUuDT/qujcSm5hpEz+NP4pz?= =?Windows-1252?Q?P8IXaSqGh7w1wRI78rDoZAQK1es+CqqbhsvRgrC2A0uDXCBZ6opXweAq?= =?Windows-1252?Q?AFWfJHDHp/hYODcRJ9hBzoPDt0LVbBEXAKtFSZmAiWkyHgC3zl0equWT?= =?Windows-1252?Q?VEIE8Ftahrf9FH9Ml/V4Y6Fcdl87SE2CwzQeJKVVFnmEsdl08zGtnReB?= =?Windows-1252?Q?aNkAH4HgPg/YdUpbQ2upNwfW9M+Miln+24KFnxEntFT777O+3mZHCJ9+?= =?Windows-1252?Q?kyOIwhaBkNfHZk3sa8q+zP6n3fL/uSQq2I8gIs4CMNBemc90Kg+UdYF4?= =?Windows-1252?Q?2otNeMjey8oDhL5dnCnJP2ZomA4YiqhxvYsH6RwnduvRVIw9bQJ0WWJb?= =?Windows-1252?Q?VKqypJtc/W4tN80g66hUv13uLnEWle8D2ERuy7oDIsiE1WURrubfuoVi?= =?Windows-1252?Q?MP8Z0TUaCN20aFVh1vRVfhKxExQi4AcOpqsOn1YKeaLB5TPdRzFQW3MS?= =?Windows-1252?Q?WNLywVAqQ+uQGMS1YF6ch0v/iN0j9Y7WGr2dIA9Vbk6asj85Tfwm+ZYB?= =?Windows-1252?Q?u1LdRK+Fxa5PrQ7RktQ8lie4Kt3deYrpbSV+UCUhwBvDUo7O9B1vI/QD?= =?Windows-1252?Q?dJVFfTL+gQSNeaKyHe5YU9vdygYZucKQhGUv4aigeKgsXYekhmOtgvUq?= =?Windows-1252?Q?wPnMqMrtCYVDtdth2wd9Zp90ir8996Lok5ppv5MUu5plDwNwcHJaV1P3?= =?Windows-1252?Q?D18hRQojjqps3bzA1QZDZpB9LcOXH0VxbB077d7g9tJ77RhFRe1RYMjc?= =?Windows-1252?Q?mZfzSsZlAEv1hE8IWUJiKZcwsGxpbGWSJKk=3D?= Content-Type: multipart/alternative; boundary="_000_DM5PR1201MB2555DB5F7942B0D18D558DF7CDC19DM5PR1201MB2555_" MIME-Version: 1.0 X-OriginatorOrg: Nvidia.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: DM5PR1201MB2555.namprd12.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: c4009a53-0018-4661-067e-08da2c1e5d3f X-MS-Exchange-CrossTenant-originalarrivaltime: 02 May 2022 09:30:15.1242 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 43083d15-7273-40c1-b7db-39efd9ccc17a X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: MiUqI4Xxxk5lJT3zDIwD6q8Ohrl+WJB7SPn88hgoWFimOFotNHiDYyGLtg1riBjrwW12oc96Td79ZdfHYpq5IQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR12MB4498 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_DM5PR1201MB2555DB5F7942B0D18D558DF7CDC19DM5PR1201MB2555_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable 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 ; Slava O= vsiienko Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK Thanks for you answer, Already red the doc on the subject but can=92t make it work in testpmd. Didn=92t implemented it myself at this step but seams I=92m missing somethi= ng. 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 Ovsii= enko 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=92m adding @Slava Ovsiienko in case you ne= ed 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_DM5PR1201MB2555DB5F7942B0D18D558DF7CDC19DM5PR1201MB2555_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable 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 <= a.pollenus@deltacast.tv>
Sent: Monday, May 2, 2022 11:53:18 AM
To: Asaf Penso <asafp@nvidia.com>; users@dpdk.org <users@dp= dk.org>; Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK=
 

Thank= s for you answer,

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

Do I need to enable a specific offload ?

 = ;

From: Asaf Penso [mailto:asafp@nvidia.co= m]
Sent: lundi 2 mai 2022 09:59
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=

 

= Hello Antoine,

=  

= Have you had a look into mlx5 documentation?

= http://doc.dpdk.org/g= uides/nics/mlx5.html

= Please look for tx_pp.

=  

= I=92m adding @Slava Ovsiienko in case yo= u 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-ubuntu= 20.04-x86_64

 

We are trying to use the DPDK tx scheduling feature o= n a ConnectX6 DX adapter. We experience some issues with the feature not wo= rking.

 

The test is using Test-pmd in txonly mode.

 

Here are the command used:

 

sudo ./dpdk-testpmd -l 0-3 -n 4 -- -i --portmask=3D0x= 1 --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 miss= ing something ?

 

I also added a print in txonly.c and clearly sees tha= t 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);

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_timestam= p on

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

 

Hope you will be able to help me.

 

Regards

 

Antoine

--_000_DM5PR1201MB2555DB5F7942B0D18D558DF7CDC19DM5PR1201MB2555_--