From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) by dpdk.org (Postfix) with ESMTP id 80EA43DC for ; Tue, 24 Apr 2018 06:14:55 +0200 (CEST) Received: by mail-lf0-f46.google.com with SMTP id g203-v6so18125383lfg.11 for ; Mon, 23 Apr 2018 21:14:55 -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=es0j+CfACUJI4AAKW14fSIMizFKqaX05gG8WQg3VSGI=; b=IWHsnegF9i7Ob7KWnVO6278e5v92Qq6QKTnssSlFXoy19mAgWwaBRILqc4sBIul8jS 21sBl6H66dX4CmYHHNQlZv/0BONzAfFD/W/TZxbg2tAg+zeIGd6R9xwY/8NxhBKa2FpW 9hZpXsXDO6Lp16/bKm4HFPL3Nu+4Vc0C+orG8uySwONJ6w147tshbcyp5WwRL10A+9J5 9PlqMVdnF849gh8RCrvvyHEfOkd6LiHVQ5iGrsnzSDEmGujMpAPStzrcM9h9RsL5V8X7 eolR13CQr0ZINze3XnukRWLX7RFchLtWikCSUPkwmJtu2vWJaNkBdag0sDxt/LidpJCv MVKA== 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=es0j+CfACUJI4AAKW14fSIMizFKqaX05gG8WQg3VSGI=; b=XXjp5BGpROFvhtJzOcXGdckSx/n1hb8orrIVbbdHxONaKMZn6sNOTOplInFPMJrsDh 5hyShljdxvk1idM6WhAJlIhPNpY0kAIVau7h2PbRIdtGllhGIHIO0VdVJh57lAFTMfph YMIhMExEDypcMGgaHoBnmJmqG7gHxKFrnrcRmkYjnKlUXYfqFPrdBzsn8kwMP1ogunIG uqoQwGVUflLKuI7oXZalwgCOnxoqdtYVndk6PfyauhVVQcD2HgpkWgZuG5kBNmMkT21G 6UNwqiY39ts0xMeKwON0H9lmu4//V81EG/nmIQPhCU7KMO5iv9hBgo5P6M8nartK3DXw s99w== X-Gm-Message-State: ALQs6tD5gHpR8CqPv5sDsbjAMVpwVA+m5+ok9gwkoYgU35Qao+uDqa/f qmi5Nr8E3qaoIWYpQP8WVAZkt/2IALW7JwRQ+6s= X-Google-Smtp-Source: AIpwx49LYqe5ZqxUOt44u3u2YWtOtq4Z2mF1vAGPf1XzpicXkVX3Hb6kwmDlDKkO3+E+Xp/WYXNk8DsRQAefpX9sfhs= X-Received: by 10.46.56.2 with SMTP id f2mr15002698lja.15.1524543294965; Mon, 23 Apr 2018 21:14:54 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:d7e3:0:0:0:0:0 with HTTP; Mon, 23 Apr 2018 21:14:54 -0700 (PDT) In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F958894836@HASMSX110.ger.corp.intel.com> References: <9B0331B6EBBD0E4684FBFAEDA55776F958894836@HASMSX110.ger.corp.intel.com> From: venkataprasad k Date: Tue, 24 Apr 2018 09:44:54 +0530 Message-ID: To: "Rosen, Rami" Cc: "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 04:14:55 -0000 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 unused=3D 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused=3D 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused=3D 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused=3D 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused=3D 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused=3D 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused=3D 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused=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 error > "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=3D21= 76, > socket=3D0 > USER1: create a new mbuf pool : n=3D779456, size=3D21= 76, > socket=3D1 > USER1: create a new mbuf pool : n=3D779456, size=3D21= 76, > socket=3D2 > USER1: create a new mbuf pool : n=3D779456, size=3D21= 76, > socket=3D3 > Done > testpmd> show config fwd > io packet forwarding - ports=3D0 - cores=3D0 - streams=3D0 - 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 =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 unused= =3D > 0000:03:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused= =3D > 0000:05:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused= =3D > 0000:05:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused= =3D > 0000:41:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused= =3D > 0000:41:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused= =3D > 0000:45:00.0 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused= =3D > 0000:45:00.1 'Ethernet Server Bypass Adapter 155d' drv=3Dvfio-pci unused= =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=3Di= gb > unused=3Dvfio-pci *Active* > 0000:01:00.1 'I350 Gigabit Network Connection 1521' if=3Denp1s0f1 drv=3Di= gb > unused=3Dvfio-pci > 0000:01:00.2 'I350 Gigabit Network Connection 1521' if=3Denp1s0f2 drv=3Di= gb > unused=3Dvfio-pci > 0000:01:00.3 'I350 Gigabit Network Connection 1521' if=3Denp1s0f3 drv=3Di= gb > 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 device= s > 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 >