[AMD Official Use Only - General] Based on the compilation command shared it looks like you are using the build in shared library mode ` gcc main.c -g `pkg-config --cflags libdpdk --libs libdpdk` Hence in EAL PCIe probe, the BNXT PMD is not triggered to identify the NIC.
Solutions for these can be 1. Build with static library ` gcc main.c -g `pkg-config --cflags libdpdk --libs --static libdpdk` 2. pass the bxnt_en PMD shared library to eal args by ` sudo ./a.out -l 1 -d librte_net_bnxt.so` Can you try any of the above ? > -----Original Message----- > From: users-requ...@dpdk.org <users-requ...@dpdk.org> > Sent: Wednesday, July 13, 2022 3:30 PM > To: users@dpdk.org > Subject: users Digest, Vol 347, Issue 6 > > [CAUTION: External Email] > > Send users mailing list submissions to > users@dpdk.org > > To subscribe or unsubscribe via the World Wide Web, visit > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dp > dk.org%2Flistinfo%2Fusers&data=05%7C01%7Cvipin.varghese%40amd.co > m%7C55465d0d4faa4cd8496a08da64b674f4%7C3dd8961fe4884e608e11a82d9 > 94e183d%7C0%7C0%7C637933032067208770%7CUnknown%7CTWFpbGZsb3d8 > eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D > %7C3000%7C%7C%7C&sdata=6JHjf2Fu%2BkQ56CF9xTZvBS%2Bh8Uomlqv > E9dq9M7VefiU%3D&reserved=0 > or, via email, send a message with subject or body 'help' to > users-requ...@dpdk.org > > You can reach the person managing the list at > users-ow...@dpdk.org > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of users digest..." > > > Today's Topics: > > 1. Re: skeleton code failing (Lokesh Chakka) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 Jul 2022 12:56:37 +0530 > From: Lokesh Chakka <lvenkatakumarcha...@gmail.com> > To: David Marchand <david.march...@redhat.com> > Cc: users <users@dpdk.org> > Subject: Re: skeleton code failing > Message-ID: > <CACh--sgKJ9B2=Nd-EUUx4D7Kz87- > nm_pwq59fy9qvnh+gbg...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Dear David, > > following is some more stuff i did > ================================================== > $ sudo dpdk-devbind.py -b vfio-pci 83:00.0 $ sudo dpdk-devbind.py -b vfio-pci > 83:00.1 $ sudo dpdk-devbind.py -b uio_pci_generic 83:00.0 83:00.1 > Error: Driver 'uio_pci_generic' is not loaded. > $ sudo dpdk-devbind.py -b igb_uio 83:00.0 83:00.1 > Error: Driver 'igb_uio' is not loaded. > $ sudo dpdk-devbind.py -b vfio-pci 83:00.0 83:00.1 > Notice: 0000:83:00.0 already bound to driver vfio-pci, skipping > Notice: 0000:83:00.1 already bound to driver vfio-pci, skipping > ================================================== > ~/Desktop/dpdk_examples/skeleton$ gcc main.c -g `pkg-config --cflags libdpdk > --libs libdpdk` lokesh@lokesh-ProLiant-DL385- > Gen10:~/Desktop/dpdk_examples/skeleton$ sudo ./a.out > EAL: Detected CPU lcores: 64 > EAL: Detected NUMA nodes: 4 > EAL: Detected shared linkage of DPDK > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket > EAL: Selected IOVA mode 'VA' > EAL: No available 1048576 kB hugepages reported > EAL: VFIO support initialized > EAL: Using IOMMU type 1 (Type 1) > EAL: Probe PCI driver: net_bnxt (14e4:1750) device: 0000:83:00.0 (socket 2) > EAL: Probe PCI driver: net_bnxt (14e4:1750) device: 0000:83:00.1 (socket 2) > TELEMETRY: No legacy callbacks, legacy socket not created Port 0 MAC: bc 97 > e1 ce 84 f0 Port 1 MAC: bc 97 e1 ce 84 f1 > > WARNING: Too many lcores enabled. Only 1 used. > WARNING, port 0 is on remote NUMA node to polling thread. > Performance will not be optimal. > WARNING, port 1 is on remote NUMA node to polling thread. > Performance will not be optimal. > > Core 0 forwarding packets. [Ctrl+C to quit] ^C > ================================================== > After a few seconds, I presses ctrl+c > > surprisingly cards are not showing up even in ifconfig. > > > > Thanks & Regards > -- > Lokesh Chakka. > > > On Wed, Jul 13, 2022 at 12:43 PM Lokesh Chakka < > lvenkatakumarcha...@gmail.com> wrote: > > > Dear David, > > > > ================================================= > > $ lspci | grep -i broadcom > > 83:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57508 > > NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb Ethernet (rev 11) > > 83:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57508 > > NetXtreme-E 10Gb/25Gb/40Gb/50Gb/100Gb/200Gb Ethernet (rev 11) $ lspci > > -n -s 83:00.0 > > 83:00.0 0200: 14e4:1750 (rev 11) > > ================================================= > > > > I am compiling my code like this : > > ================================================= > > gcc main.c `pkg-config --cflags libdpdk --libs libdpdk` > > ================================================= > > > > Hence it is statically linked code. > > If I try > > $ dpdk-pmdinfo.py ./a.out > > > > But I am not seeing any output > > > > > > > > Thanks & Regards > > -- > > Lokesh Chakka. > > > > > > On Wed, Jul 13, 2022 at 12:22 PM David Marchand > > <david.march...@redhat.com> > > wrote: > > > >> On Wed, Jul 13, 2022 at 7:35 AM Lokesh Chakka > >> <lvenkatakumarcha...@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 > >> > >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmails.dp > dk.org%2Farchives%2Fusers%2Fattachments%2F20220713%2Fa362f7fe%2Fatta > chment- > 0001.htm&data=05%7C01%7Cvipin.varghese%40amd.com%7C55465d0d4f > aa4cd8496a08da64b674f4%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C > 0%7C637933032067208770%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA > wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C > %7C&sdata=jXnaf1qrCA5VSCMyrPPc5S5WYsHveR1tNBL4lczkGVE%3D&am > p;reserved=0> > > End of users Digest, Vol 347, Issue 6 > *************************************
