From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: "Guelce, Guevenc" <guevenc.guelce@sap.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: RE: Enabling multiport eswitch (mlx5) breaks PF1 bifurcation immediately
Date: Wed, 19 Jun 2024 18:12:33 +0000 [thread overview]
Message-ID: <PH0PR12MB8800628C8DB74AA686B0CE70A4CF2@PH0PR12MB8800.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PA4PR02MB7103BEB93727AA059AD890D68DC22@PA4PR02MB7103.eurprd02.prod.outlook.com>
Hi,
> From: Guelce, Guevenc <guevenc.guelce@sap.com>
> Sent: Friday, June 14, 2024 11:18
> To: users@dpdk.org
> Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Subject: Enabling multiport eswitch (mlx5) breaks PF1 bifurcation immediately
> Hi all, Hi Dariusz,
>
>
> Thanks a lot for your help so far. We really appreciate it.
> I just want to touch base with this question which was asked by my colleague Tao a while back.
>
> Our question is actually quite simple. Issuing the commands listed below on a ConnectX-6 Dx Card breaks the
> bifurcated nature of the mlx5 driver in linux kernel for PF1. (No traffic is forwarded to linux kernel anymore on PF1)
> You don’t need to start any testpmd or dpdk application. Just issuing the following commands below breaks the PF1
> in linux kernel already.
>
> sudo devlink dev eswitch set pci/0000:8a:00.0 mode switchdev
> sudo devlink dev eswitch set pci/0000:8a:00.1 mode switchdev
> sudo devlink dev param set pci/0000:8a:00.0 name esw_multiport value true cmode runtime
> sudo devlink dev param set pci/0000:8a:00.1 name esw_multiport value true cmode runtime
>
>
> ----<test environment>-----
> pci/0000:8a:00.0:
> driver mlx5_core
> versions:
> fixed:
> fw.psid MT_0000000359
> running:
> fw.version 22.39.2048
> fw 22.39.2048
> Linux kernel version: 6.6.16
> DPDK: 23.11 (But not really needed to reproduce the issue)
> ----</test environment>------
>
>
> This makes the eswitch multiport feature for us unusable. Could you please advise whether we are missing smt here ?
> As we are really keen to use this feature.
Could you please send us the following info? It would help with debugging the issue.
- Despite the Multiport E-Switch configuration, do you configure any additional bonding?
- Output of commands:
- sudo devlink dev param show
- for f in /sys/kernel/debug/mlx5/0000:8a:00.0/lag/*; do echo $f; cat $f; done
- for f in /sys/kernel/debug/mlx5/0000:8a:00.1/lag/*; do echo $f; cat $f; done
- Output of dmesg, ideally all logs since boot.
>
> Thanks & Regards
>
>
> Guvenc Gulce
>
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2024-06-19 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 9:18 Guelce, Guevenc
2024-06-19 18:12 ` Dariusz Sosnowski [this message]
2024-06-20 15:34 ` Guelce, Guevenc
2024-06-24 12:57 ` Dariusz Sosnowski
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=PH0PR12MB8800628C8DB74AA686B0CE70A4CF2@PH0PR12MB8800.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=guevenc.guelce@sap.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).