DPDK usage discussions
 help / color / mirror / Atom feed
From: venkataprasad k <prasaddml@gmail.com>
To: "Rosen, Rami" <rami.rosen@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] testpmd + EAL: No probed ethernet devices + dpdk-17.11.1
Date: Tue, 24 Apr 2018 18:46:07 +0530	[thread overview]
Message-ID: <CABFMH+doMO=bxYFMym+4A2dLp2o==wu5CcA0cEtepMEB6gsxkg@mail.gmail.com> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F958A01CE9@HASMSX110.ger.corp.intel.com>

Thanks for your reply.
After setting CONFIG_RTE_LIBRTE_IXGBE_BYPASS in the config, it started
working.

here is the log:
[root@localhost dpdk-stable-17.11.1]# ./build/app/testpmd –l 12,13,14 –n 4
-- -i
EAL: Detected 80 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:01:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:01:00.2 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:01:00.3 on NUMA socket 0
EAL:   probe driver: 8086:1521 net_e1000_igb
EAL: PCI device 0000:03:00.0 on NUMA socket 0
EAL:   probe driver: 8086:155d net_ixgbe
EAL: PCI device 0000:03:00.1 on NUMA socket 0
EAL:   probe driver: 8086:155d net_ixgbe
EAL: PCI device 0000:05:00.0 on NUMA socket 0
EAL:   probe driver: 8086:155d net_ixgbe
EAL: PCI device 0000:05:00.1 on NUMA socket 0
EAL:   probe driver: 8086:155d net_ixgbe
EAL: PCI device 0000:41:00.0 on NUMA socket 1
EAL:   probe driver: 8086:155d net_ixgbe
EAL: PCI device 0000:41:00.1 on NUMA socket 1
EAL:   probe driver: 8086:155d net_ixgbe
EAL: PCI device 0000:45:00.0 on NUMA socket 1
EAL:   probe driver: 8086:155d net_ixgbe
EAL: PCI device 0000:45:00.1 on NUMA socket 1
EAL:   probe driver: 8086:155d net_ixgbe


Thanks,
Venkat


On Tue, Apr 24, 2018 at 6:01 PM, Rosen, Rami <rami.rosen@intel.com> wrote:

> Hi, Venkat,
>
>
>
> In DPDK 17.11.1 stable, which is the one you use, support for
>
> 8086:155D depends on that
>
> CONFIG_RTE_LIBRTE_IXGBE_BYPASS is set.
>
>
>
> See:
>
>
>
> In drivers/net/ixgbe/ixgbe_bypass_defines.h
>
>
>
> /* extractions from ixgbe_type.h */
>
> #define IXGBE_DEV_ID_82599_BYPASS       0x155D
>
>
>
>
>
> /* extractions from ixgbe_type.h */
>
> #define IXGBE_DEV_ID_82599_BYPASS       0x155D
>
>
>
> In drivers/net/ixgbe/ixgbe_ethdev.c:
>
> /*
>
> * The set of PCI devices this driver supports
>
> */
>
> static const struct rte_pci_id pci_id_ixgbe_map[] = {
>
> ...
>
> #ifdef RTE_LIBRTE_IXGBE_BYPASS
>
>         { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID,
> IXGBE_DEV_ID_82599_BYPASS) },
>
> #endif
>
> …
>
>
>
> By default, CONFIG_RTE_LIBRTE_IXGBE_BYPASS is not set in DPDK 17.11.1
>
>
>
>
>
> Please check:
>
> $more  build/.config | grep CONFIG_RTE_LIBRTE_IXGBE_BYPASS
>
> Do you get the following ?
>
> CONFIG_RTE_LIBRTE_IXGBE_BYPASS=n
>
>
>
> In case you do, maybe try to change it to
>
> CONFIG_RTE_LIBRTE_IXGBE_BYPASS=y
>
> and run make clean and make for the DPDK tree, and then bind and run
> testpmd app again, and post here the log.
>
>
>
> Regards,
>
> Rami Rosen
>
>
>
>
>
>
>
> *From:* venkataprasad k [mailto:prasaddml@gmail.com]
> *Sent:* Tuesday, April 24, 2018 12:24
> *To:* Stephen Hemminger <stephen@networkplumber.org>
> *Cc:* Rosen, Rami <rami.rosen@intel.com>; users@dpdk.org
> *Subject:* Re: [dpdk-users] testpmd + EAL: No probed ethernet devices +
> dpdk-17.11.1
>
>
>
> I believe these are supported by DPDK.
>
> here is the lspci output.
>
>
>
> [root@localhost dpdk-stable-17.11.1]# lspci -nn | grep 155d
>
> 03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
> 03:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
> 05:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
> 05:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
> 41:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
> 41:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
> 45:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
> 45:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Server
> Bypass Adapter [8086:155d] (rev 01)
>
>
>
> Network devices using DPDK-compatible driver
>
> ============================================
>
> 0000:03:00.0 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
> 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
> 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
> 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
> 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
> 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
> 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
> 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=igb_uio unused=
>
>
>
> Thanks,
>
> Venkat
>
>
>
>
>
> On Tue, Apr 24, 2018 at 10:36 AM, Stephen Hemminger <
> stephen@networkplumber.org> wrote:
>
> On Tue, 24 Apr 2018 09:44:54 +0530
> venkataprasad k <prasaddml@gmail.com> wrote:
>
> > Hi Rami,
> >
> > Thanks for your reply.
> > yes. i already did the binding and here is the output.
> > [root@localhost dpdk-stable-17.11.1]# ./usertools/dpdk-devbind.py -s
> >
> > Network devices using DPDK-compatible driver
> > ============================================
> > 0000:03:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> >
> > Network devices using kernel driver
> > ===================================
> > 0000:01:00.0 'I350 Gigabit Network Connection 1521' if=enp1s0f0 drv=igb
> > unused=vfio-pci *Active*
> > 0000:01:00.1 'I350 Gigabit Network Connection 1521' if=enp1s0f1 drv=igb
> > unused=vfio-pci
> > 0000:01:00.2 'I350 Gigabit Network Connection 1521' if=enp1s0f2 drv=igb
> > unused=vfio-pci
> > 0000:01:00.3 'I350 Gigabit Network Connection 1521' if=enp1s0f3 drv=igb
> > unused=vfio-pci
> >
> > Other Network devices
> > =====================
> > <none>
> >
> > similarly tried with igb_uio as well, but i see the same result ( "EAL:
> No
> > probed ethernet devices" )
> >
> > Thanks,
> > Venkat
> >
> >
> > On Mon, Apr 23, 2018 at 9:55 PM, Rosen, Rami <rami.rosen@intel.com>
> wrote:
> >
> > > Hi,
> > > You need to bind a device to DPDK before launching testpmd, with the
> > > usertools/dpdk-devbind.py script. Did you do it? What is the output
> > > of
> > > ./usertools/dpdk-devbind.py -s
> > > on your host ? do you see any entries under "Network devices using
> > > DPDK-compatible driver" when running ./usertools/dpdk-devbind.py -s?
> > >
> > > Please take a look in the "Linux Getting Started Guide", section
> > > 4.4: "Binding and Unbinding Network Ports to/from the Kernel Modules"
> > >
> > > http://dpdk.org/doc/guides/linux_gsg/linux_drivers.html#
> <http://dpdk.org/doc/guides/linux_gsg/linux_drivers.html>
> > > binding-and-unbinding-network-ports-to-from-the-kernel-modules
> > >
> > > Regards,
> > > Rami Rosen
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: users [mailto:users-bounces@dpdk.org] On Behalf Of
> venkataprasad k
> > > Sent: Monday, April 23, 2018 15:35
> > > To: users@dpdk.org
> > > Subject: [dpdk-users] testpmd + EAL: No probed ethernet devices +
> > > dpdk-17.11.1
> > >
> > > Hello,
> > >
> > > I am trying to run testpmd application and getting the following error
> > > "EAL: No probed ethernet devices"
> > >
> > > version: dpdk-stable-17.11.1
> > > Log:
> > > [root@localhost dpdk-stable-17.11.1]#  ./build/app/testpmd –l
> 12,13,14 –n
> > > 4
> > > -- -i
> > > EAL: Detected 80 lcore(s)
> > > EAL: No free hugepages reported in hugepages-1048576kB
> > > EAL: Probing VFIO support...
> > > EAL: VFIO support initialized
> > > EAL: PCI device 0000:01:00.0 on NUMA socket 0
> > > EAL:   probe driver: 8086:1521 net_e1000_igb
> > > EAL: PCI device 0000:01:00.1 on NUMA socket 0
> > > EAL:   probe driver: 8086:1521 net_e1000_igb
> > > EAL: PCI device 0000:01:00.2 on NUMA socket 0
> > > EAL:   probe driver: 8086:1521 net_e1000_igb
> > > EAL: PCI device 0000:01:00.3 on NUMA socket 0
> > > EAL:   probe driver: 8086:1521 net_e1000_igb
> > > *EAL: No probed ethernet devices*
> > > Interactive-mode selected
> > > USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=779456,
> size=2176,
> > > socket=0
> > > USER1: create a new mbuf pool <mbuf_pool_socket_1>: n=779456,
> size=2176,
> > > socket=1
> > > USER1: create a new mbuf pool <mbuf_pool_socket_2>: n=779456,
> size=2176,
> > > socket=2
> > > USER1: create a new mbuf pool <mbuf_pool_socket_3>: n=779456,
> size=2176,
> > > socket=3
> > > Done
> > > testpmd> show config fwd
> > > io packet forwarding - ports=0 - cores=0 - streams=0 - NUMA support
> > > enabled, MP over anonymous pages disabled
> > >
> > > testpmd>
> > >
> > >
> > > from the dpdk-setup script, i see there are devices supported by dpdk
> > >
> > > Network devices using DPDK-compatible driver
> ==============================
> > > ==============
> > > 0000:03:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > > 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > > 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > > 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > > 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > > 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > > 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > > 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=vfio-pci unused=
> > >
> > > Network devices using kernel driver
> > > ===================================
> > > 0000:01:00.0 'I350 Gigabit Network Connection 1521' if=enp1s0f0 drv=igb
> > > unused=vfio-pci *Active*
> > > 0000:01:00.1 'I350 Gigabit Network Connection 1521' if=enp1s0f1 drv=igb
> > > unused=vfio-pci
> > > 0000:01:00.2 'I350 Gigabit Network Connection 1521' if=enp1s0f2 drv=igb
> > > unused=vfio-pci
> > > 0000:01:00.3 'I350 Gigabit Network Connection 1521' if=enp1s0f3 drv=igb
> > > unused=vfio-pci
> > >
> > > Other Network devices
> > > =====================
> > > <none>
> > >
> > > My understanding is, it should consider the devices under "Network
> devices
> > > using DPDK-compatible driver", but it is not.
> > > The nic that i am using Intel 82599, which is supported by dpdk.
> > >
> > > can someone help me to understand what is wrong here?
> > >
> > > Thanks,
> > > Venkat
> > >
>
> Check the PCI id's of the devices. I have seen in older releases
> where there are some subtypes of Intel Ethernet devices
> which are supported by Linux kernel, but not yet in DPDK driver table
> (and in some cases small changes to MAC code are needed).
>
>
>

      reply	other threads:[~2018-04-24 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 12:35 venkataprasad k
2018-04-23 16:25 ` Rosen, Rami
2018-04-24  4:14   ` venkataprasad k
2018-04-24  5:06     ` Stephen Hemminger
2018-04-24  9:23       ` venkataprasad k
2018-04-24 12:31         ` Rosen, Rami
2018-04-24 13:16           ` venkataprasad k [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='CABFMH+doMO=bxYFMym+4A2dLp2o==wu5CcA0cEtepMEB6gsxkg@mail.gmail.com' \
    --to=prasaddml@gmail.com \
    --cc=rami.rosen@intel.com \
    --cc=stephen@networkplumber.org \
    --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).