From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com [209.85.215.45]) by dpdk.org (Postfix) with ESMTP id 1C1F22AA0 for ; Tue, 24 Apr 2018 15:16:09 +0200 (CEST) Received: by mail-lf0-f45.google.com with SMTP id z130-v6so20257033lff.5 for ; Tue, 24 Apr 2018 06:16:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=H1gVZKtIZ9cbRaYlngq1J9mDIrJ1nP1RfQ4tTQFt+tY=; b=bNzBDu5+L90wPAmjD39o2mPMbIh9D1AlqNymZwQLdigS1D8TxHSdr/dOIUBVD4Vrll ikLejgRQIskitGcXtfl3v6X2Cw9AoyJKXaXqlASU39wRKZgLh7bff6RLzGapE9x3Ws31 GiMZbZYaiVrGZ6DK9U0jNoN/dLytk2zTPMGDGsmudK1AnSvzTNRPJAfumtzcirUFbuIn zgtk2m6uBRvp+FIP1jfHjmJGi0a/I4r9mtVuI+FW1flD2hOL7Kl8MYIWg6dxXGgbVKDP 2ERBlFHtZzGGtRPR6l8vzr9ZqPIxwzwdOp+6oPhIBewOiAOzMmzla1NEA31q6rAAaqd3 tQug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=H1gVZKtIZ9cbRaYlngq1J9mDIrJ1nP1RfQ4tTQFt+tY=; b=kxYvJ7MIuDC/9IgbKstRfGkowRNndDlwOrcPZvUTXh0Q8xQbIBm+YSffumxmiOIudI TNnzR5UxgGpS1CfOkeuXvFg0ZAo622DtNiEtWOI+Rl+Xa15aZflVEeyMow5PZ+sRRfoe +mewPiYXFDdbBD6Ee3kTU7nAxRCZVEdrMTEDEP4w5cnTRXoKXiOem+pReoVwXW+E7hWo 1tZRl6w9W8O4ms8S1NMl70o6msCR6Jp4IDx3ljoz48iSelKp3jqsQ/baZ4C+hMX1LbML OWhklyiINodMO9elA1t3t4WDn6qshYH+tUFkZOmbU8FHljWbuzII0bP+g8aJS4++iUtc V5dw== X-Gm-Message-State: ALQs6tDnfjTumbFibeYlh2pCG82tyTTEYrxLQGRADQlTTg5onbWdjFqj UBp+hAsH5i6ureADERyNf4PMMHhszb67LL+PxTY= X-Google-Smtp-Source: AIpwx48UgN8x+SktD+wFuyeNj7sQwptsUo4srLFug5x0n7lkcToTbZfEBzBUHGHBBEzAH474UeTy0zV4smAqqrKZW9c= X-Received: by 10.46.45.10 with SMTP id t10mr16102929ljt.110.1524575768329; Tue, 24 Apr 2018 06:16:08 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:d7e3:0:0:0:0:0 with HTTP; Tue, 24 Apr 2018 06:16:07 -0700 (PDT) In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F958A01CE9@HASMSX110.ger.corp.intel.com> References: <9B0331B6EBBD0E4684FBFAEDA55776F958894836@HASMSX110.ger.corp.intel.com> <20180423220611.6ef54ef6@xeon-e3> <9B0331B6EBBD0E4684FBFAEDA55776F958A01CE9@HASMSX110.ger.corp.intel.com> From: venkataprasad k Date: Tue, 24 Apr 2018 18:46:07 +0530 Message-ID: To: "Rosen, Rami" Cc: Stephen Hemminger , "users@dpdk.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] testpmd + EAL: No probed ethernet devices + dpdk-17.11.1 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 13:16:09 -0000 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 =E2=80=93l 12,13,= 14 =E2=80=93n 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 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[] =3D { > > ... > > #ifdef RTE_LIBRTE_IXGBE_BYPASS > > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, > IXGBE_DEV_ID_82599_BYPASS) }, > > #endif > > =E2=80=A6 > > > > 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=3Dn > > > > In case you do, maybe try to change it to > > CONFIG_RTE_LIBRTE_IXGBE_BYPASS=3Dy > > 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 > *Cc:* Rosen, Rami ; 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 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 0000:03:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Digb_uio unused= =3D > > > > 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 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 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 0000:03:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unuse= d=3D > > > > Network devices using kernel driver > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 0000:01:00.0 'I350 Gigabit Network Connection 1521' if=3Denp1s0f0 drv= =3Digb > > unused=3Dvfio-pci *Active* > > 0000:01:00.1 'I350 Gigabit Network Connection 1521' if=3Denp1s0f1 drv= =3Digb > > unused=3Dvfio-pci > > 0000:01:00.2 'I350 Gigabit Network Connection 1521' if=3Denp1s0f2 drv= =3Digb > > unused=3Dvfio-pci > > 0000:01:00.3 'I350 Gigabit Network Connection 1521' if=3Denp1s0f3 drv= =3Digb > > unused=3Dvfio-pci > > > > Other Network devices > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > 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 > 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# > > > > 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 erro= r > > > "EAL: No probed ethernet devices" > > > > > > version: dpdk-stable-17.11.1 > > > Log: > > > [root@localhost dpdk-stable-17.11.1]# ./build/app/testpmd =E2=80=93l > 12,13,14 =E2=80=93n > > > 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 : n=3D779456, > size=3D2176, > > > socket=3D0 > > > USER1: create a new mbuf pool : n=3D779456, > size=3D2176, > > > socket=3D1 > > > USER1: create a new mbuf pool : n=3D779456, > size=3D2176, > > > socket=3D2 > > > USER1: create a new mbuf pool : n=3D779456, > size=3D2176, > > > socket=3D3 > > > Done > > > testpmd> show config fwd > > > io packet forwarding - ports=3D0 - cores=3D0 - streams=3D0 - NUMA sup= port > > > 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 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > 0000:03:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unu= sed=3D > > > > > > Network devices using kernel driver > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > 0000:01:00.0 'I350 Gigabit Network Connection 1521' if=3Denp1s0f0 drv= =3Digb > > > unused=3Dvfio-pci *Active* > > > 0000:01:00.1 'I350 Gigabit Network Connection 1521' if=3Denp1s0f1 drv= =3Digb > > > unused=3Dvfio-pci > > > 0000:01:00.2 'I350 Gigabit Network Connection 1521' if=3Denp1s0f2 drv= =3Digb > > > unused=3Dvfio-pci > > > 0000:01:00.3 'I350 Gigabit Network Connection 1521' if=3Denp1s0f3 drv= =3Digb > > > unused=3Dvfio-pci > > > > > > Other Network devices > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > > > > 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). > > >