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 CC1A3A0503 for ; Thu, 19 May 2022 06:40:01 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7DE3A40150; Thu, 19 May 2022 06:40:01 +0200 (CEST) Received: from NAM02-BN1-obe.outbound.protection.outlook.com (mail-bn1nam07on2040.outbound.protection.outlook.com [40.107.212.40]) by mails.dpdk.org (Postfix) with ESMTP id 4E40940140 for ; Thu, 19 May 2022 06:39:59 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DxcSJb7ZdRyr1UTUVP/dw9JOnrLfdcxBU899EV7lLtRHsRjtmG46ZtCtToa8i1UxMKdFbbfoGxXtTNMtQJT+r+L2lsbTUmm+/HjfpudkE+pmN2Aoxw3Zx6EGV2ssUHqQtPDeXYeaNfOrgeDBG38rLxXZxNz/WvUDvGUJN+TENzfmrMR5wL3qlMExVUPVGo6eTOjxwS/uOx7UXK1MDMAwuHBzUUdO3t8lepePIpb5+TUvil+BVzxtbYSiNPy7Pgus3HW51WmmxoIp7hyqWY64lGnTvppjelw0xz6KDdxIo3fZ+f8MpQFnvR4khCphp+SZLEo98tzMRH93sL8nuXLGtA== 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=j7L9HRj/7fCkwrL+m/Eba3AeZNMlDH/RNCBr0MUUYew=; b=cOiVyRXs+8deI1MM3Xngf6nZGpbpgn6uUcz23w0jOeAzRFzfO6JRltXHlbM2IvglnaW3vcrlJBAmU/EZp2etnKQXazxkg1m3lZVDbR7iwzSORhTF4MfdDA+jpnkU1wGcQZWsrCjusS87Sl+ToJhDs8RYNPmfKiUY4Ny3+V37Wubo6Cocgs1Kf05DR2WOSVkyAw4NXXGVY4yKuGXaTfPm8Fpjmk0qY4GYg+XGnvNvelBGxx5PZqV6Y/je6u/JtgOgWSqs2m4b2Xcj3wMQTmTnT6Nh57ytZyNRyFfHF4QgKvfWRJHb6d5XuYRIyVNSrNwaJC0F0lOManIdPW/98cbcYA== 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=j7L9HRj/7fCkwrL+m/Eba3AeZNMlDH/RNCBr0MUUYew=; b=q0ISenpt7RtRy4bcvRKmOx9djIeUqoQQM8Vhfh3qFuIWx9OlFAE8w3LpAr7csfSam7QnVMibNjp99JDzRY2UAicOWoF6aAfDroTK2kvL9sJ//b7rvafqZWb8PB4glvTndBsg3Y4O5GwevAHuR273e45IB1WjYQaRiOzxfN/e0QIErkRlcnUpylmMQC7tq4XE7kulAtTUY/P8EzTDr6qrkoNoS4hI7NDWvcj97BFq99JB1BsXMDG8PwKhdLnE93RrIqFZ1RHwviB/TyOthvh4UMi1aoworM+iL9siLE0FnxnjmpFEuzrJka8xOjClm7g4igpKUTUHZSvi/p7+aD6Ebw== Received: from DM5PR1201MB2555.namprd12.prod.outlook.com (2603:10b6:3:ea::14) by BN6PR1201MB0161.namprd12.prod.outlook.com (2603:10b6:405:55::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5273.15; Thu, 19 May 2022 04:39:57 +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.5250.018; Thu, 19 May 2022 04:39:57 +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/2VXQAAHbviAAAVrRtAAEW18QA0hEWog= Date: Thu, 19 May 2022 04:39:57 +0000 Message-ID: References: <686a7825fb9d4e3e8516b3d3600756ac@deltacast.tv> In-Reply-To: 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: e425f4c6-ed53-42f0-e4b8-08da3951a047 x-ms-traffictypediagnostic: BN6PR1201MB0161: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: fB5jzWpIBRskSnxRP4Ee/QnDL8PpaITAtAKMYY4b08bJxJHUg57nU/2Pa1eSK6Zs8fM5MbqquE8FDMS48L/OEZ/lVJDNOvBczi5THOeDYnkRT3/Wgy30Qvg+5YeBgq3ic0BKzH6UyGFrK2tj7GV00b9fgrdeiHJJr35a1RdB1Ytm3J+O8vA7jv+8fsb742+7TWYO2Qx2/ljuudPQKrkbvKYDeWAorwmruEoRCkiLKO69Sekp1XfXLyOEu9qU6yAvkocEzdh305LTb2J3QkeuAXBqey577Jbt3YZJEb4TyAAcgng3B4gzzXlnGhbmW75RzIONMe0rBfoyyVUzmiQavEz3POMDsRCPxBicPZVSLd2oBsSb0TsG41EQ/kchemOFXKtUV3i2O2GJjU9c4iJEmaeooPUAA5NH0GWEJBdP+EgDXRYohPRSYePimpjKjXdZRdykBKpOMPWpbwMO2mtaGW71Lr77qcgSQ42m7G7EcDYxH+No+WEpyQzK9JQQwJUv4NRyKRGR84doO39A6ke2SFlvAo36nSjf6CCvV8nqEex/l/Gl+EhiCsyajCcO878+jLKrebeYwbEEJ6CCYtOPKdxoAFqAPyLcwF4dvTcnROZYWHZNbuCObD4shFhQbJwANbyW10Q+l8/e+b0T4O9c0FZY91HX6H6ysCxQ0nd/xxoSvntYrDmjr8pWleKdxDqnTUAK5z7EvgYBAkNKCmsFG0+lMRCHV2D6NAQhXcqbFbxfeaS1R7YDZKXWPwfO8JRlYmiU5oscDPf3gXHIS771JaGuwemZd+PiDCY22nMaafxNuTeBx4HT6hs1h8eUgDlk 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)(64756008)(76116006)(66556008)(66446008)(66946007)(38100700002)(66476007)(91956017)(38070700005)(122000001)(8676002)(166002)(71200400001)(110136005)(19627235002)(508600001)(86362001)(966005)(53546011)(7696005)(33656002)(316002)(6636002)(6506007)(26005)(55016003)(5660300002)(9686003)(21615005)(2906002)(186003)(52536014)(8936002)(562404015); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?WRdfEOQ/UzIuAoITNjNd7G1JU+KnvX/ljUiduILKfecA2aL4JVRFlyyc?= =?Windows-1252?Q?th9bvWct1rg1Da4CU0o2WjfHPf66URNolflsTG2INhaYcb7W0crIhHpa?= =?Windows-1252?Q?jgrPNuW4YxsDJZQ8US4gMgxlAAJ/rV/A3anAQ7eLO/6jFrQc3ylhQUkG?= =?Windows-1252?Q?mRuGaMOWMKrYuR473OO1VmBYv4Gkn+cHIE+fIA8z2pRfjZjYoYeIfMah?= =?Windows-1252?Q?9bxIJqJnqOsHmtzfqmzjahE0Buux9S/PVn3hWWcoX8X7c5caTcqo5tLe?= =?Windows-1252?Q?cZoCk1AAcdhpzf6BM7uZGzZEVK0Qnc6jK1Mp0lGkKFchV/QStFAg1m68?= =?Windows-1252?Q?pipvl6Vvbb2T6+8rVm72psDSpeJKCDZJggIKsKxbS1S6cKfISCQ6s94F?= =?Windows-1252?Q?I6obbv0PGOHm61bISf5v6etGAYDWyO4nsTzDUxhoyRwWdxtVLNks1grK?= =?Windows-1252?Q?ccV5fza+uUogD/CZbkEs1fSlmR9wA/sPbHrC/KBAxC+oNLdidIseEmtd?= =?Windows-1252?Q?3RoAmyhlkxPIWcjJpoDOkURw2B35WPpNTomYQqH9Oqr/e49XdmSEc0+Z?= =?Windows-1252?Q?ZDG6CURr3TET+nuzs7pLKHtQnRsHrwUIRGk4L/AQwfdRoWlsicEu5A2u?= =?Windows-1252?Q?YG0cvXaFXbjsEUzd7Ojs7uhb2KSVskF/+u7HT2pSbX81NcnWf4qepj2s?= =?Windows-1252?Q?DD9FPFPpNBsEa0CT/kVq8wsGYhDVa5agmIR2KK8QjhVUfRC7zK1JEFUN?= =?Windows-1252?Q?DTYzJMB94jT2s1n38Guy9dMbBjoKHz9LB6eQ/xaeZsj2uxG95VLAUpDP?= =?Windows-1252?Q?KJ1HenjqtUbqtfFdNIF3gV3kmV3XcJHxa7h/sdtnb+gNht8usIQCtPeJ?= =?Windows-1252?Q?zjSi9tpPtSDjIj98ECioVuV6jR2m6QNpQWboZ7X+Lp8Sus+O9GJ+jg1H?= =?Windows-1252?Q?d1ByBZ/XO8eul8cneRevgpleeAJJMTpphEIAEa2DvFUBiq/IbLEEnuaT?= =?Windows-1252?Q?KhYvAh3az38+qMeUFJgDdkdpRzMtY2B/ZfbjyrBoPXyv3+pPlSB6PL6J?= =?Windows-1252?Q?TTfkstvfVAQHYVUWKUxDl1rWBrKWfus65DVk1utPKX5RWCAjG0T45PAc?= =?Windows-1252?Q?7EyA2w8rRvQ8CIvpdW92yJb1OcHY+oaGH5hfc4MSQ23bCQBQoZTPh16m?= =?Windows-1252?Q?pnTb2BWx1S/QD3jb5RNZtMT67PEH53QJXFzKLkRzL6Y+4ab3B8QfzUgP?= =?Windows-1252?Q?hc9J9Fwmrhmz/xO8LewPxA71ZzDaDDLlG9gROaxuRbGu8DYrbKi/tJSY?= =?Windows-1252?Q?BKsYmnY/syukDfW7NNmvXo/PfltnJuzy1gr1RICklSpX0jDzBeHuDn7y?= =?Windows-1252?Q?OUGlT7BHnaIF4h/u+8ewBP1xJtHX9xmoiqhRjv/eg7EptwxMydplKYu+?= =?Windows-1252?Q?Xi4bYrjDZjZvWvKAivMlCyv08oH8LqgLhMYDmomRgmHYtmX/4MTRfdnk?= =?Windows-1252?Q?Sk9ps0XPIAEs+T8PquuxxlGyVQO1v1HeCELd8j6gwKxgyoo62Ajrsogi?= =?Windows-1252?Q?e+BuxYbTB+8TA8Difv5qALWYu/NyS+zVLk3D+zbc6QQk6CfRxInWCui3?= =?Windows-1252?Q?KQdEweQo/A28zlrZS5o1GG0ukJgelb9d8Z3wKrY0reVxyhITmbhMS85O?= =?Windows-1252?Q?xg3UZ3v8Zx0yRUkoiJPDQBdts6z9hXmfOw9ynfQ377wYybUsupVlOwij?= =?Windows-1252?Q?Q/jVq5Q3vDI5YgLYz+9V7f7MYAKIJ+cqGW9CH0ylzKfomfF9z5sanF/I?= =?Windows-1252?Q?drtTCHJ3WTNFnyYgzkzcC1vH2Xxkhoczuij2Zb6lagq3Bb8axymrh/+E?= =?Windows-1252?Q?FPlSkTefyRxYug6ksskt49Uc5I3sPUG1Y/Q=3D?= Content-Type: multipart/alternative; boundary="_000_DM5PR1201MB2555893E3B08819BABAAAB6BCDD09DM5PR1201MB2555_" 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: e425f4c6-ed53-42f0-e4b8-08da3951a047 X-MS-Exchange-CrossTenant-originalarrivaltime: 19 May 2022 04:39:57.0234 (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: G4dJWlOoFvupHEpASVVUcd17B1LMNbXiSRbvaeS7F6fu7hkZJxh3HsXIsxeeNlbV6OUM13ojo3hBMk76p1QNCA== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1201MB0161 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_DM5PR1201MB2555893E3B08819BABAAAB6BCDD09DM5PR1201MB2555_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Example: dpdk-testpmd -c 0x7ffc0000 -n 4 -a d8:00.1, tx_pp=3D1 -a d8:00.0,tx_pp=3D1-= -burst=3D64 --txd=3D256 --rxd=3D256 --mbcache=3D512 --rxq=3D2 --txq=3D2 --n= b-cores=3D1 --no-lsc-interrupt -i --auto-start --rss-udp You can read more about testpmd and the specific mlx5 devargs for tx_pp her= e: http://doc.dpdk.org/guides/nics/mlx5.html Regards, Asaf Penso ________________________________ From: Antoine POLLENUS Sent: Monday, May 2, 2022 2:36:10 PM To: Asaf Penso ; users@dpdk.org ; Slava O= vsiienko Subject: RE: [ConnectX 6Dx]Issue using Tx scheduling feature in DPDK I=92m 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=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 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=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_DM5PR1201MB2555893E3B08819BABAAAB6BCDD09DM5PR1201MB2555_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Example:

dpdk-testpmd -c 0x7ffc0000 -n 4 -a d8:00= .1, tx_pp=3D1 -a d8:00.0,tx_pp=3D1--burst=3D64 --txd=3D2= 56 --rxd=3D256 --mbcache=3D512 --rxq=3D2 --txq=3D2 --nb-cores=3D1 --no-lsc-= interrupt -i --auto-start --rss-udp

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

Regards,
Asaf Penso
From: Antoine POLLENUS <= a.pollenus@deltacast.tv>
Sent: Monday, May 2, 2022 2:36:10 PM
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=
 

I=92m not really f= amiliar with testpmd, how am I supposed to do that ?

 

F= rom: 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 = see you add the tx_pp devarg as part of the testpmd command line.

 

Regards,

Asaf Penso

Fro= m: 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=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 <= 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=

 

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 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-ubunt= u20.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 w= orking.

 

The test is using Test-pmd in txonly mode.

 

Here are the command used:

 

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

 

I also added a print in txonly.c and clearly sees th= at 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_mbu= f_dynflag_lookup) returns -1

 

I also tried to enabled the feature.

 

testpmd> port config 0 tx_offload send_on_timesta= mp 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

--_000_DM5PR1201MB2555893E3B08819BABAAAB6BCDD09DM5PR1201MB2555_--