DPDK usage discussions
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
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
Date: Tue, 18 Oct 2022 06:04:14 +0000	[thread overview]
Message-ID: <DM4PR12MB53737ACD10C61C64B181C512A1289@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM5PR1201MB255597C7B84036E55092C7B7CD5C9@DM5PR1201MB2555.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2343 bytes --]

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>
Sent: Thursday, October 6, 2022 14:45
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 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 #2: Type: text/html, Size: 13439 bytes --]

  parent reply	other threads:[~2022-10-18  6:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 13:24 Haider Ali
2022-10-06  6:44 ` Asaf Penso
2022-10-06  7:48   ` Haider Ali
2022-10-18  6:04   ` Xueming(Steven) Li [this message]
2022-10-18  6:10     ` Haider Ali
2022-10-18  6:30       ` Xueming(Steven) Li
2022-10-19 10:30         ` Haider Ali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM4PR12MB53737ACD10C61C64B181C512A1289@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=asafp@nvidia.com \
    --cc=haider@dreambigsemi.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).