Re: mlx5 - shared_rxq not working on some Connect x6 DX

[Haider Ali <haider@dreambigsemi.com>]

[-- Attachment #1.1: Type: text/plain, Size: 4413 bytes --]

Thanks Xueming.

I have updated my firmware and now shared_rxq is working. Please add a note if possible in your dpdk documents like the below for minimum requirements of firmware and OFED version for shared_rxq.

[cid:1f21cc59-3850-4bcb-a8c6-bd4f9ffaef4b]

Regards,
Haider
________________________________
From: Xueming(Steven) Li <xuemingl@nvidia.com>
Sent: Tuesday, October 18, 2022 11:30 AM
To: Haider Ali <haider@dreambigsemi.com>
Cc: users <users@dpdk.org>; Asaf Penso <asafp@nvidia.com>
Subject: RE: mlx5 - shared_rxq not working on some Connect x6 DX


Hi Haider:



From your first post, ofed version of B is higher, you are right. Fw version is lower – please ignore 16 and 22 prefix which is NIC type.



version: 5.4-3.1.0

firmware-version: 16.32.1010 (MT_0000000080)



version: 5.4-3.5.8

firmware-version: 22.31.1014 (MT_0000000436)



Thanks,

Xueming





From: Haider Ali <haider@dreambigsemi.com>
Sent: Tuesday, October 18, 2022 14:11
To: Xueming(Steven) Li <xuemingl@nvidia.com>
Cc: users <users@dpdk.org>; Asaf Penso <asafp@nvidia.com>
Subject: Re: mlx5 - shared_rxq not working on some Connect x6 DX



Server B has higher versions of OFED and firmware than server A. Please let me know if are you asking me to downgrade OFED and firmware on server B.



Have you removed shared RXQ features in higher versions of OFED and firmware?



Regards,

Haider

________________________________

From: Xueming(Steven) Li <xuemingl@nvidia.com<mailto:xuemingl@nvidia.com>>
Sent: Tuesday, October 18, 2022 11:04 AM
To: Haider Ali <haider@dreambigsemi.com<mailto:haider@dreambigsemi.com>>
Cc: users <users@dpdk.org<mailto:users@dpdk.org>>; Asaf Penso <asafp@nvidia.com<mailto:asafp@nvidia.com>>
Subject: RE: mlx5 - shared_rxq not working on some Connect x6 DX



Hi Haider,



The device capability is critical to support shared RXQ.

The OFED and firmware version of server B seems not up to date, could please align with server A?



Best Regards,

Xueming Li



From: Asaf Penso <asafp@nvidia.com<mailto:asafp@nvidia.com>>
Sent: Thursday, October 6, 2022 14:45
To: Haider Ali <haider@dreambigsemi.com<mailto:haider@dreambigsemi.com>>; users <users@dpdk.org<mailto: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 the use case?

What do you try to achieve and whether you see any issue?



Regards,

Asaf Penso

________________________________

From: Haider Ali <haider@dreambigsemi.com<mailto:haider@dreambigsemi.com>>
Sent: Tuesday, October 4, 2022 4:24:03 PM
To: users <users@dpdk.org<mailto:users@dpdk.org>>
Cc: Asaf Penso <asafp@nvidia.com<mailto: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 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 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_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 configurations we need to apply?



Regards,

Haider

[-- Attachment #1.2: Type: text/html, Size: 18018 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 12182 bytes --]