From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Sankalpa Timilsina <sankalpatimilsina12@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Unable to recognize master/representor on the multiple IB devices
Date: Sun, 23 May 2021 00:13:01 +0000 [thread overview]
Message-ID: <DM4PR12MB5373975C513DEE842E94117CA1279@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAE3YagLjiYpcjSxHuj=7YEsF8r0qpkQvqbcD_jiB3AqrN3nguw@mail.gmail.com>
Hi Sankalpa,
Have you enabled SRIOV and switchdev mode correctly? Is there any error in demsg?
Here is the regular steps:
1. enable sriov - new VF ports shown in `ip link`
2. unbind VFs - new VF ports disappear
3. enable switchdev mode - new representor ports shown in `ip link`
4. bind VFs again or passthrough to VM
Best Regards,
Xueming
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Sankalpa Timilsina
> Sent: Sunday, May 23, 2021 2:43 AM
> To: users@dpdk.org
> Subject: [dpdk-users] Unable to recognize master/representor on the multiple IB devices
>
> Hi, I am getting a DPDK MLX5 probing issue.
>
> 1. I have installed the mlx5/ofed driver
> 2. I have loaded the kernel modules.
>
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: No available hugepages reported in hugepages-2048kB
> EAL: Probing VFIO support...
> EAL: Probe PCI driver: mlx5_pci (15b3:1013) device: 0000:5e:00.0 (socket 0)
> mlx5_pci: unable to recognize master/representors on the multiple IB devices
> common_mlx5: Failed to load driver = mlx5_pci.
>
> EAL: Requested device 0000:5e:00.0 cannot be used
> EAL: Bus (pci) probe failed.
>
> As for the 'failing to load mlx5_pci' driver, I can see that the mlx5_core driver is loaded.
>
> dpdk-devbind.py -s
>
> Network devices using kernel driver
> ===================================
> 0000:5e:00.0 'MT27700 Family [ConnectX-4]' if=enp94s0 drv=mlx5_core unused=
>
> What does failing to recognize master/representors on multiple IB devices mean?
>
> My configuration is: CentOS 7.9, Linux Kernel 5.12, OFED 4.9 (LTS)
next prev parent reply other threads:[~2021-05-23 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 18:42 Sankalpa Timilsina
2021-05-23 0:13 ` Xueming(Steven) Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-22 17:58 Sankalpa Timilsina
2021-05-27 7:05 ` Asaf Penso
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=DM4PR12MB5373975C513DEE842E94117CA1279@DM4PR12MB5373.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=sankalpatimilsina12@gmail.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).