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 C6DB2A0544 for ; Sun, 9 Oct 2022 23:42:10 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C6BA7410D1; Sun, 9 Oct 2022 23:42:06 +0200 (CEST) Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2065.outbound.protection.outlook.com [40.107.220.65]) by mails.dpdk.org (Postfix) with ESMTP id 78E6641153 for ; Thu, 6 Oct 2022 09:48:31 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U0W8nvdVsGMF77hjeSbTu80uI8hq0srh9M3YlrQyqoOadZXjsEg65UVPP+eP/FhKXMobNUYebOC2N6DM7PNVD4aLdOpcPeO8dAwaiqHrw979vCisNu/J2zttq1QP6D1ksztyNNUtoOiN3fEM1O8gOuYq/a+rTV6YHwWJf49+M9If995sBd8DNN3Q4cr2CSQqinMwnQwZKoKIfEUe6FA4xdcOEbkSjlbRB59IaAAh1J88L8nnpjiB+TyHQOs6j+LLgyv9b1EPXm3tvRKqPtC8LB4zP/mzUcchkdcvqKwpDEussmV4LU+joidnwwY2OYwdGdfIw/mpEDkviQCrWBqN4A== 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=kJlGbgsrliuqL+/h7r9rbuqB1TDXByT0qzfA9MPzyvE=; b=ayJ1zHZVYHCGDeBwc/ZR5Si/4kShlgzS3ACUd6laQLET8BqptyZTB01cUQ0wG1tRMc4X2X2usmJnZ9xzBT/1pbbbHu9lXDrqotigtPgNBs9V/3wszeqXPFE3T98v1U1h3TqqKInVsvRo2yyg/XhoCArzqQf34rs+RZn4RiZp7hUNq/qAcXX9lc14Z9YwX82W27t/OWImfyhymqA+6V05tiyc5wl3xn1y//JuszUUrv9IIGCb9/gMrkojTOoFe6P2pURH7v5QvBjJtoJKlmRcm56q4EknoB1rnOIxPBEJyyp3z39iBpcUPOxBoIy+PR4953KQDO3+ebS/7WwjiApJ4Q== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=dreambigsemi.com; dmarc=pass action=none header.from=dreambigsemi.com; dkim=pass header.d=dreambigsemi.com; arc=none Received: from MW5PR22MB3395.namprd22.prod.outlook.com (2603:10b6:303:1c1::9) by BL1PR22MB3684.namprd22.prod.outlook.com (2603:10b6:208:397::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5676.32; Thu, 6 Oct 2022 07:48:27 +0000 Received: from MW5PR22MB3395.namprd22.prod.outlook.com ([fe80::9d63:f798:bcd3:c3bd]) by MW5PR22MB3395.namprd22.prod.outlook.com ([fe80::9d63:f798:bcd3:c3bd%3]) with mapi id 15.20.5676.031; Thu, 6 Oct 2022 07:48:27 +0000 From: Haider Ali To: Asaf Penso , users Subject: Re: mlx5 - shared_rxq not working on some Connect x6 DX Thread-Topic: mlx5 - shared_rxq not working on some Connect x6 DX Thread-Index: AQHY1/KIRADhX+c+QkOsD60Zv/hgY64A7bGxgAAFdY0= Date: Thu, 6 Oct 2022 07:48:26 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=dreambigsemi.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: MW5PR22MB3395:EE_|BL1PR22MB3684:EE_ x-ms-office365-filtering-correlation-id: 95439095-dd95-45b5-1ac3-08daa76f274c x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: I9kLDZ/9yClB0/X0A21SgHeyDHOD/wvDfCUpl3EYonYetPDwGx2gJxi2Jk21VYyDUaahjF1iqcsGl4dvtMv4EXNEN3byhy3CHY6Mh50CJolxYItPsxJzp5/Vhpl4Mb0bzegbFH14XnFAQCa1iP7Aubo0/wA5F1MUsAH73CASxvgrh3NYxxTNbDOFyQEMYhPSyXJQoW6mj8Rnb3xXSO1Cgq803IFiTvEGJkPb6HWMu0CGXUjjQLoHbsoCfeP5G309DowukS01LNaAElLDu9LoQGdUb4fiTXMBkunSeIp7/9GNxnG9fy8BARdsGLxuGPtcFAN/X6XG0vKt5RGm6vE6Rq4qaanbsZNYx5niSPedB8QO/S/xfxUvRSvg2GW12tMZoT0fqOgNSxLlu6yJUPSvfLpdZiNyYbM8hk7++lUC6/5eqPnEC6z2kxIjfKp859fmMLS0CwftzKkjk9V6soBu27rmc0/tMCEYG4CFyPNXUFcTQAFe38/78KXKlAKgQefD/fjUG7GCdwDIggCWCv0nhcH9V3+iYOMFy+8jVjOXsI7PDnoroAWDteZn9TkEH3kuQ3hym6nx5mFFBJtoUrGPtLiarO3GVOqK77u4KAuqR9BQ9C+xjVLPLZghXyNHBOFOrgnfYEbq8XWN6d4rDdRAt0XEx2XyXObKhTbI6/cuXVDgf/mdNEDb4QjfuSuphyDpp6jPbMce7ypjNt9HvAmEM62GevwRDXE13rSzCLX77npSDElLtFgzSG7LDquTO4HnJX0Ye+gH6msR9TvUAEKsWg== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW5PR22MB3395.namprd22.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230022)(396003)(366004)(376002)(39830400003)(346002)(136003)(451199015)(71200400001)(2906002)(86362001)(186003)(19627405001)(52536014)(83380400001)(41300700001)(122000001)(110136005)(38070700005)(9686003)(8936002)(26005)(55016003)(5660300002)(64756008)(66446008)(7696005)(8676002)(66476007)(66556008)(53546011)(33656002)(478600001)(76116006)(316002)(6506007)(66946007)(38100700002)(91956017); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?bowFsu6w3kuLI3rKFlzkS36hgqCOY9WRkJFv+d3vy6DkM63JfC5wwGtH2XOL?= =?us-ascii?Q?om9XbmCAWGW+/K8bB7Wvxu79gyvHZ+adP0WcrV8g+6y84c79bRPUbIVyLbVz?= =?us-ascii?Q?J9JLMwG9t0xBwlWyFfwEgUxv9kc5gCOpV/iv4VnRnc099TeP0DDiGUuQPUF9?= =?us-ascii?Q?RlD2Osa8iSjOydV5q4MVbLyPwyYtOAVbD6UNqOAkHgYhG/jRTgyhKqwgX8XT?= =?us-ascii?Q?2nO7hRqHNbgE1c6tk/Luarq13UUN0P9+515g1JN9gas0v29eDWT09yJ/Bdfk?= =?us-ascii?Q?dr/qhw2pXbhGLt/dwLKO5kZ2QRzFB81/dxM9F3H80BYG3wRsp3X2QyIUVR1s?= =?us-ascii?Q?LOS78dPLqN4LkW5hGopARDTj3TNLDIZnTaug+CDl3ZKtvyO8a2jd8zExzq7N?= =?us-ascii?Q?zAsStx4TXrKQ3aJTlxApCu8TLF9rLVKjEadqhERkMMj566MRp/WQS5E7fI+X?= =?us-ascii?Q?6gPkrLgcjSPqqzyMW/RjG8kPCoMFKBTHnM3XIemww3ls2kg+cQTt2Ll6iYuE?= =?us-ascii?Q?W/BJmKyf1gf8BzKOq5grTTQUsOuv8QfwSCDlg59WWIXKz5GLUJbtuO3R4zN7?= =?us-ascii?Q?JlmJomEohoJLwvFKnpqtTwL+QkeECRdAnHwcleKCqBnfdzOjgpQacd6g7ylL?= =?us-ascii?Q?u/UsIz28Xnlt2EereOp6SZxBOjN8BTCG+D0QxLiTyKlKG6iMBKZRiW04Mw+o?= =?us-ascii?Q?Q8CgB+s6/r4xHofpPqY5+VqzejpEAboCf1iNtgol41gFaY+GQ9uyy1iiq2si?= =?us-ascii?Q?iy2ZlagdyWsabCsjkUwSy1DZOj8HVTwqeqSWdiprGUlB6H4g3Wdc+Rlb8xeZ?= =?us-ascii?Q?50wHNjriNO1hu8YIX9uCsdLaLrH3nkw2C5TEqpn9oiWYwfYgrAi1aFiyPQBm?= =?us-ascii?Q?C7k0VoPtBS6mjTEbfueWRR1TW+L4cHgEMaKpSRHix99uR5FsasgfxacsEHLT?= =?us-ascii?Q?mVqZkLqw9K3XzGA32hlwauTrwjoDtTnGaAEoeK3GXDfBvtVgvk2bPWBp+UPz?= =?us-ascii?Q?r5t2dow1AtP2ojlrxPh1e2AD2DlR6EJxLbpXc1Hd/gZCZ6qGVR4L47bthwu6?= =?us-ascii?Q?OKjRamxUaptle1tzy6VhwYOYlqHRK+oDVdt6ZTX1iN7i/UFcY5yuKyPg0Kip?= =?us-ascii?Q?Ck463jYMX6avu/t6HrTDWER0oyNTWqwIk15MRly1AwhQWZWb5vTtG35p96f5?= =?us-ascii?Q?Cv7hFzHHB7tQjAY2lsflmFEHAl5xJB7BAXPFp9fF3IS1S8rjPmE6nt3N1j+E?= =?us-ascii?Q?uBfXBCV4dJIRgFWVAr4QZ2P3XEXXhLAoxPpoIMixum/LJR7jhLuYAfU0uHt+?= =?us-ascii?Q?Rk9FHYp9cFrHPGIJHcRovtypElazN9ypnBPmX3/SI+ljokUGUveHaK6MZP0w?= =?us-ascii?Q?3EuMaipDQyrOmDLu0C+pb7sgiIIezZrS5tCoFaMlXP1JJ0r06O03TY5+YT9f?= =?us-ascii?Q?9OAYfLinpKzzDACSQMQ+GytpEdVyvdY41q6ybaSkBPjvYEbu5AkOKRqNjmH4?= =?us-ascii?Q?YXTab1nEPek1tRMdNXzvTnTuBGQrZfPiLLcHFGKWVmJp1anFQvWFn5sZ1MHR?= =?us-ascii?Q?NXtZ9NYf6uTxwRG7h+JueLUY3Xh5Pe27BpMneEpK?= Content-Type: multipart/alternative; boundary="_000_MW5PR22MB3395BDBFC6C722F8844994B6A75C9MW5PR22MB3395namp_" MIME-Version: 1.0 X-OriginatorOrg: dreambigsemi.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: MW5PR22MB3395.namprd22.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 95439095-dd95-45b5-1ac3-08daa76f274c X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Oct 2022 07:48:26.8698 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: f492af1f-9d8c-414b-ac8c-6732fc0649d5 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: xL4mW16oQoLQBisC5xb69dS6VsTvale8TC9alYCygt7Zf8O9zfwo9C87yDQzVFz6IVFzT2CyXvdRTKP5v/qxMQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL1PR22MB3684 X-Mailman-Approved-At: Sun, 09 Oct 2022 23:42:05 +0200 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_MW5PR22MB3395BDBFC6C722F8844994B6A75C9MW5PR22MB3395namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks Asaf for your reply. We want to use shared_rxqs between PF and VF_rep. I tried to test this feat= ure with the testpmd shared_rxq fwd. We used the "--rxq-share" option in th= e command line to run the testpmd. With server A, we were able to create sh= ared_rxqs between PF and VF_rep0, but with server B we were not able to cre= ate shared_rxqs instead server B created individual RX queues on PF and VF_= rep0. We confirmed this by printing the stats of both ports. As in mlx5 doc "Shared Rx queue: Counters of received packets and bytes num= ber of devices in same share group are same. Counters of received packets a= nd bytes number of queues in same group and queue ID are same." As PF and VF_rep0 should have the same RX stats, by printing port stats ser= ver A shows the same stats on both PF and VF_rep but server B doesn't. Plea= se review the below test configurations and port stats on both servers. Configurations on SERVER A and SERVER B: $ sudo ./build_22_07/app/dpdk-testpmd -l 0-1 -n 4 -a 0000:04:00.0,represent= or=3Dvf[0] -- -i --nb-cores=3D1 --rxq-share=3D2 mlx5_common: DevX create q counter set failed errno=3D22 status=3D0 syndrom= e=3D0 mlx5_common: DevX create q counter set failed errno=3D22 status=3D0 syndrom= e=3D0 testpmd> set fwd shared_rxq testpmd> start SEND PACKET FROM SCAPY: The packet sent from the wire is received on PF but port stats of both were= updated correctly: sendp(Ether()/Dot1Q(vlan=3D123)/IP()/UDP(),iface=3D'enp130s0f0',count=3D24) SHOW STATS ON SERVER A: testpmd> show port stats all ######################## NIC statistics for port 0 #####################= ### RX-packets: 24 RX-missed: 0 RX-bytes: 1440 RX-errors: 0 RX-nombuf: 0 TX-packets: 0 TX-errors: 0 TX-bytes: 0 Throughput (since last show) Rx-pps: 0 Rx-bps: 0 Tx-pps: 0 Tx-bps: 0 #########################################################################= ### ######################## NIC statistics for port 1 #####################= ### RX-packets: 24 RX-missed: 0 RX-bytes: 1440 RX-errors: 0 RX-nombuf: 0 TX-packets: 0 TX-errors: 0 TX-bytes: 0 Throughput (since last show) Rx-pps: 0 Rx-bps: 0 Tx-pps: 0 Tx-bps: 0 #########################################################################= ### SHOW STATS ON SERVER B: testpmd> show port stats all ######################## NIC statistics for port 0 #####################= ### RX-packets: 24 RX-missed: 0 RX-bytes: 1440 RX-errors: 0 RX-nombuf: 0 TX-packets: 0 TX-errors: 0 TX-bytes: 0 Throughput (since last show) Rx-pps: 1 Rx-bps: 808 Tx-pps: 0 Tx-bps: 0 #########################################################################= ### ######################## NIC statistics for port 1 #####################= ### RX-packets: 0 RX-missed: 0 RX-bytes: 0 RX-errors: 0 RX-nombuf: 0 TX-packets: 0 TX-errors: 0 TX-bytes: 0 Throughput (since last show) Rx-pps: 0 Rx-bps: 0 Tx-pps: 0 Tx-bps: 0 #########################################################################= ### Regards, Haider ________________________________ From: Asaf Penso Sent: Thursday, October 6, 2022 11:44 AM To: Haider Ali ; users Subject: Re: mlx5 - shared_rxq not working on some Connect x6 DX Hello Haider, Besides the info print issue, can you describe what is the use case? What do you try to achieve and whether you see any issue? Regards, Asaf Penso ________________________________ From: Haider Ali Sent: Tuesday, October 4, 2022 4:24:03 PM To: users Cc: Asaf Penso Subject: mlx5 - shared_rxq not working on some Connect x6 DX Hi, I used two servers A and B. Server A has Connect x5 and x6 DX cards while s= erver B has Connect x6 DX card. I have checked with Connect x5 and x6 DX cards on "server A" and I am able = to get below rxq_share device capability: testpmd> show port info all Device capabilities: 0x14( RXQ_SHARE FLOW_SHARED_OBJECT_KEEP ) Server A setting: # ofed_info -s MLNX_OFED_LINUX-5.4-3.1.0.0: # ethtool -i enp129s0f0 driver: mlx5_core version: 5.4-3.1.0 firmware-version: 16.32.1010 (MT_0000000080) expansion-rom-version: bus-info: 0000:81:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes But when I moved to server B with another Connect x6 DX card, I could not s= ee this capability. testpmd> show port info all Device capabilities: 0x14( FLOW_SHARED_OBJECT_KEEP ) Server B Settings: # ofed_info -s MLNX_OFED_LINUX-5.4-3.5.8.0: # ethtool -i enp132s0f0 driver: mlx5_core version: 5.4-3.5.8 firmware-version: 22.31.1014 (MT_0000000436) expansion-rom-version: bus-info: 0000:84:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes Although server B has higher versions of OFED and firmware, my question is = do I need to enable/disable firmware settings? Or are there any other confi= gurations we need to apply? Regards, Haider --_000_MW5PR22MB3395BDBFC6C722F8844994B6A75C9MW5PR22MB3395namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Thanks Asaf for your reply.

We want to use shared_rxqs between PF and VF_rep. I tried to test this feat= ure with the testpmd shared_rxq fwd. We used the "--rxq-share" option in the command line to run the testpmd. With server A, we were able to create shared= _rxqs between PF and VF_rep0, but with server B we were not able to create shared_rxqs instead server B crea= ted individual RX queues on PF and VF_rep0. We confirmed this by printing t= he stats of both ports.  

As in ml= x5 doc "Shared Rx queue: Counters of received packets and bytes num= ber of devices in same share group are same. Counters of received packets and bytes number of queues in same group and = queue ID are same."

As PF and VF_rep= 0 should have the same RX stats, by printing port stats server = A shows the same stats on both PF and VF_rep but server B doesn't. Please review the below test co= nfigurations and port stats on both servers.

Configurations on SERVER A and SERVER B:
$ sudo ./build_22_07/app/dpdk-testpmd -l 0-1 -n 4 -a 0000:04:00.0,represent= or=3Dvf[0] -- -i --nb-cores=3D1 --rxq-share=3D2
mlx5_common: DevX create q counter set failed errno=3D22 status=3D0 syndrom= e=3D0
mlx5_common: DevX create q counter set failed errno=3D22 status=3D0 syndrom= e=3D0

testpmd> set fwd shared_rxq
testpmd> start

SEND PACKET FROM SCAPY:
The packet sent from the wire is received on PF but port stats of= both were updated correctly:
sendp(Ether()/Dot1Q(vlan=3D123)/IP()/UDP(),iface=3D'enp130s0f0',count=3D24)=

SHOW STATS ON SERVER A:
testpmd> show port stats all

  ######################## NIC statisti= cs for port 0  ########################
  RX-packets: 24   =       RX-missed: 0          RX-byte= s:  1440
  RX-errors: 0
  RX-nombuf:  0     &nbs= p;  
  TX-packets: 0   &= nbsp;      TX-errors: 0          TX= -bytes:  0

  Throughput (since last show)
  Rx-pps:     =        0          Rx-bps: &nbs= p;          0
  Tx-pps:         &= nbsp;  0          Tx-bps:      = ;      0
  #####################################= #######################################

  ######################## NIC statisti= cs for port 1  ########################
  RX-packets: 24       &= nbsp; RX-missed: 0          RX-bytes:  1440
  RX-errors: 0
  RX-nombuf:  0     &nbs= p;  
  TX-packets: 0       &n= bsp;  TX-errors: 0          TX-bytes:  0=

  Throughput (since last show)
  Rx-pps:         &= nbsp;  0          Rx-bps:      = ;      0
  Tx-pps:         &= nbsp;  0          Tx-bps:      = ;      0
  #####################################= #######################################

SHOW STATS ON SERVER B:

testpmd> show port stats all

  ######################## NIC statisti= cs for port 0  ########################
  RX-packets: 24       &= nbsp; RX-missed: 0          RX-bytes:  1440
  RX-errors: 0
  RX-nombuf:  0     &nbs= p;  
  TX-packets: 0       &n= bsp;  TX-errors: 0          TX-bytes:  0=

  Throughput (since last show)
  Rx-pps:         &= nbsp;  1          Rx-bps:      = ;    808
  Tx-pps:         &= nbsp;  0          Tx-bps:      = ;      0
  #####################################= #######################################

  ######################## NIC statisti= cs for port 1  ########################
  RX-packets: 0       &n= bsp;  RX-missed: 0          RX-bytes:  0=
  RX-errors: 0
  RX-nombuf:  0     &nbs= p;  
  TX-packets: 0       &n= bsp;  TX-errors: 0          TX-bytes:  0=

  Throughput (since last show)
  Rx-pps:         &= nbsp;  0          Rx-bps:      = ;      0
  Tx-pps:         &= nbsp;  0          Tx-bps:      = ;      0
  #####################################= #######################################

Regards,
Haider
From: Asaf Penso <asafp@= nvidia.com>
Sent: Thursday, October 6, 2022 11:44 AM
To: Haider Ali <haider@dreambigsemi.com>; users <users@dpdk= .org>
Subject: Re: mlx5 - shared_rxq not working on some Connect x6 DX
 
Hello Haider,
Besides the info print issue, can you describe what is th= e use case?
What do you try to achieve and whether you see any issue?=

Regards,
Asaf Penso
From: Haider Ali <haid= er@dreambigsemi.com>
Sent: Tuesday, October 4, 2022 4:24:03 PM
To: users <users@dpdk.org>
Cc: Asaf Penso <asafp@nvidia.com>
Subject: mlx5 - shared_rxq not working on some Connect x6 DX
 
Hi,

I used two servers A and B. Server A has Connect x5 and x6 DX cards while server B has = Connect x6 DX card.

I have checked with Connect x5 and x6 DX = cards on "server A" and I am able to get below rxq_share device c= apability:

testpmd> show port info all

Device capabilities: 0x14( RXQ_SHARE FLOW_SHARED_OBJECT_KEEP )

Server A setting:
# ofed_info -s
MLNX_OFED_LINUX-5.4-3.1.0.0:

# ethtool -i enp129s0f0
driver: mlx5_core
version: 5.4-3.1.0
firmware-version: 16.32.1010 (MT_00000= 00080)
expansion-rom-version:
bus-info: 0000:81:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes


But when I moved to server B with another= Connect x6 DX card, I could not see this capability.

testpmd> show port info all

Device capabilities: 0x14( FLOW_SHARED_OBJECT_KEEP )

Server B Settings:
# ofed_info -s
MLNX_OFED_LINUX-5.4-3.5.8.0:

# ethtool -i enp132s0f0
driver: mlx5_core
version: 5.4-3.5.8
firmware-version: 22.31.1014 (MT_00000= 00436)
expansion-rom-version:
bus-info: 0000:84:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes


Although server B has higher versions = of OFED and firmware, my question is do I need to enable/disable firmware s= ettings? Or are there any other configurations we need to apply?

Regards,
Haider
--_000_MW5PR22MB3395BDBFC6C722F8844994B6A75C9MW5PR22MB3395namp_--