From: Thomas Monjalon <thomas@monjalon.net>
To: CJ Sculti <cj@cj.gy>
Cc: users@dpdk.org, Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: Re: DPDK with Mellanox ConnectX-5, complaining about mlx5_eth?
Date: Wed, 13 Nov 2024 22:26:38 +0100 [thread overview]
Message-ID: <9487809.CDJkKcVGEf@thomas> (raw)
In-Reply-To: <CANvjkS9Ft73Oa=7PYaKthUSJKv5TVq5SkNb7vdRLaCer4xXJDw@mail.gmail.com>
13/11/2024 21:10, CJ Sculti:
> I've been running my application for years on igb_uio with Intel NICs. I
> recently replaced them with a Mellanox ConnectX-5 2x 40gbps NIC, updated
> the DPDK version my application uses, and compiled with support for mlx5
> PMDs. Both 40Gbps ports are up with link, and both are in Ethernet mode,
> not Infiniband mode. However, I'm getting complaints when I start my
> application about trying to load 'mlx5_eth'? Both are bound to mlx5_core
> driver at the moment. When I bind them to vfio-pci, or uio_pci_generic, my
> application fails to recognize them at all as valid DPDK devices. Anyone
> have any ideas? Also, strange that it only complains about one? I have them
> configured in a bond on the kernel, as my application requires that.
You must not bind mlx5 devices with VFIO.
I recommend reading documentation.
You can start here:
https://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#bifurcated-driver
then
https://doc.dpdk.org/guides/platform/mlx5.html#design
next prev parent reply other threads:[~2024-11-13 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 20:10 CJ Sculti
2024-11-13 21:26 ` Thomas Monjalon [this message]
2024-11-13 21:43 ` CJ Sculti
2024-11-13 22:43 ` Thomas Monjalon
2024-11-14 2:10 ` Yasuhiro Ohara
2024-11-14 16:10 ` CJ Sculti
2024-11-14 20:16 ` Thomas Monjalon
2024-11-15 10:11 ` Yasuhiro Ohara
2024-11-18 17:33 ` CJ Sculti
2024-11-18 17:46 ` Thomas Monjalon
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=9487809.CDJkKcVGEf@thomas \
--to=thomas@monjalon.net \
--cc=cj@cj.gy \
--cc=dsosnowski@nvidia.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).