DPDK usage discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: skeleton code failing
Date: Wed, 13 Jul 2022 08:52:18 +0200	[thread overview]
Message-ID: <CAJFAV8xc0OYKdV3f6Kz-8--6_4EfkXm_fSK6+FMb28vsRLBNEw@mail.gmail.com> (raw)
In-Reply-To: <CACh--sgyv8mffcFVfwCDJmXOvUKDp9sMPveHZRPYuj-Wrp4hhA@mail.gmail.com>

On Wed, Jul 13, 2022 at 7:35 AM Lokesh Chakka
<lvenkatakumarchakka@gmail.com> wrote:
> Would like to understand if I am missing something. I am new to this platform.
> rte_eth_dev_count_avail is returning zero.
> OS is Ubuntu 22.04. DPDK is latest version.
> Cards are being detected by Linux. Ifconfig is showing the cards up. LED is also glowing.

Indeed, DPDK provides a userspace driver for some NetXtreme nics
(which is net/bnxt).
This userspace driver does not rely on the bnxt Linux kernel driver.
IOW, this card being detecting and working with the Linux kernel does
not automatically mean that this nic can work with DPDK.

We need more info on your nic, first.

Can you share the pci id of this nic (like running lspci -n -s $pci_address)?
It should be a 14e4:XXXX.

Then you can check this XXXX against what your dpdk application supports.

If it is a statically linked application, you can run:
$ dpdk-pmdinfo.py /path/to/your/application

Else, if your application is dynamically linked against DPDK driver,
you can run this command against the net/bnxt driver .so.22 (for 21.11
and later releases):
$ dpdk-pmdinfo.py /path/to/your/dpdk/drivers/librte_net_bnxt.so.22

You should get a list of supported NetXtreme nics, like:

[snipped some other drivers compiled in my application]
PMD NAME: net_bnxt
PMD HW SUPPORT:
 Broadcom Inc. and subsidiaries (14e4) : BCM5745X NetXtreme-E RDMA
Virtual Function (1606) (All Subdevices)
 Broadcom Inc. and subsidiaries (14e4) : BCM5745X NetXtreme-E Ethernet
Virtual Function (1609) (All Subdevices)
 Broadcom Inc. and subsidiaries (14e4) : BCM57454 NetXtreme-E
10Gb/25Gb/40Gb/50Gb/100Gb Ethernet (1614) (All Subdevices)
 Broadcom Inc. and subsidiaries (14e4) : NetXtreme-E RDMA Virtual
Function (16c1) (All Subdevices)
 Broadcom Inc. and subsidiaries (14e4) : NetXtreme-C Ethernet Virtual
Function (16cb) (All Subdevices)
[snipped the rest]

I hope you can find a (XXXX) corresponding to your NIC.


-- 
David Marchand


  reply	other threads:[~2022-07-13  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  5:59 Lokesh Chakka
2022-07-13  5:35 ` Lokesh Chakka
2022-07-13  6:52   ` David Marchand [this message]
2022-07-13  7:13     ` Lokesh Chakka
2022-07-13  7:26       ` Lokesh Chakka
2022-08-26  4:35         ` Lokesh Chakka

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=CAJFAV8xc0OYKdV3f6Kz-8--6_4EfkXm_fSK6+FMb28vsRLBNEw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=lvenkatakumarchakka@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).