DPDK usage discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: animesh tripathi <anitrip.444@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: RE: Mellaox nic binding to driver.
Date: Thu, 7 Oct 2021 07:31:51 +0000	[thread overview]
Message-ID: <DM4PR12MB5312B0457DE6156D79D050FCCFB19@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAMH6JP87+FskGO0WAdgB4p80cj8-GsQA2FcoQB3Ge_Gtn7KqBA@mail.gmail.com>

Hi,

> -----Original Message-----
> From: animesh tripathi <anitrip.444@gmail.com>
> Sent: Thursday, October 7, 2021 8:19 AM
> To: users@dpdk.org
> Subject: Mellaox nic binding to driver.
> 
> Hi Team,
> 
> Do I need to bind the mellanox nic to any driver to use it with dpdk. In case of
> intel, I am binding the pcie with igb_uio driver
For Mellanox NIC's you don't need to bind them to igb_uio,
need to keep them bounded to their original kernel driver mlx5_core.
> 
> In case of mellanox nic, if I am binding the mellanox nic to igb_io, I am getting
> the following error:
> 
> EAL: Detected 24 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Auto-detected process type: PRIMARY
> EAL: Detected static linkage of DPDK
> EAL: Multi-process socket /var/run/dpdk/nr_dpdk/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: VFIO support initialized
> EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:b5:00.0 (socket 0)
> mlx5_net: no Verbs device matches PCI device 0000:b5:00.0, are kernel
> drivers loaded?
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device 0000:b5:00.0 cannot be used
> EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: 0000:b5:00.1 (socket 0)
> mlx5_net: no Verbs device matches PCI device 0000:b5:00.1, are kernel
> drivers loaded?
> mlx5_common: Failed to load driver mlx5_eth
> EAL: Requested device 0000:b5:00.1 cannot be used
> TELEMETRY: No legacy callbacks, legacy socket not created No of ports : 0
> Calling DPDK-Init for PDCP
> 
> But when I do not bind the mellanox nic to any driver, it is working fine.
> 
> Please let me know if my approach is correct.
> 
> Thanks,
> Animesh Tripathi

Kindest regards
Raslan Darawsheh

      reply	other threads:[~2021-10-07  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07  5:18 animesh tripathi
2021-10-07  7:31 ` Raslan Darawsheh [this message]

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=DM4PR12MB5312B0457DE6156D79D050FCCFB19@DM4PR12MB5312.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=anitrip.444@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).