From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f176.google.com (mail-ob0-f176.google.com [209.85.214.176]) by dpdk.org (Postfix) with ESMTP id C4D977EC4 for ; Fri, 7 Nov 2014 18:46:36 +0100 (CET) Received: by mail-ob0-f176.google.com with SMTP id va2so2928924obc.21 for ; Fri, 07 Nov 2014 09:56:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dbvpdPq2vo+O21VRa1z7rJmDmg+ujwleZRwZ0woBFzo=; b=0z6TYBq4C9uoVFoXUBc0d4o0/jx326rEPDcFsCbnbcSGCA9zke8BCiIBxcqdc11prw haPP1+MqsvOCWMuAkoVQ2UyjS+5sPPf4hITwwJDu9cfExVB59XyNnh5Yb3TrYrEveA44 4ZRhB0NH3wz7uFztx65+qMSMTWI7Ox/mZo3jcHIQN8zdKvvxkKu9U7+RUKiXTYIenNKd 3O0UXl6nYHtBObMNTooyp1J2dC0NQcrFX8wZ+85RDz0pz2uP+26Ui549XabQ1nvwRL6f g0gSCruIwouzf3wROwItOS9RU2qLnnz+CfbKW04uWYjZ8C/U1kIm2Zhv781j1E0FSafL 6pjw== MIME-Version: 1.0 X-Received: by 10.182.20.195 with SMTP id p3mr10811980obe.42.1415382968853; Fri, 07 Nov 2014 09:56:08 -0800 (PST) Received: by 10.202.232.66 with HTTP; Fri, 7 Nov 2014 09:56:08 -0800 (PST) In-Reply-To: <20141107153053.GA10376@bricha3-MOBL3> References: <20141105101246.GA9856@bricha3-MOBL3> <20141107153053.GA10376@bricha3-MOBL3> Date: Fri, 7 Nov 2014 23:26:08 +0530 Message-ID: From: Manoj Viswanath To: Bruce Richardson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: dev@dpdk.org Subject: Re: [dpdk-dev] Ports not detected by IGB_UIO in DPDK 1.7.1 in QEMU_KVM environment X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 17:46:37 -0000 Hi Bruce, Please find my comment in lined. On Fri, Nov 7, 2014 at 9:00 PM, Bruce Richardson wrote: > On Fri, Nov 07, 2014 at 08:31:34PM +0530, Manoj Viswanath wrote: > > Hi Bruce, > > > > I was not doing anything specific for binding the NICs to IGB_UIO (like > > invoking "dpdk_nic_bind.py" script explicitly) when using my applicatio= n > > with DPDK 1.6.0. The e1000 devices assigned via virt-manager to the VM > were > > automatically getting picked up and initialized by IGB_UIO within each > VM. > > > > The same is not working with DPDK 1.7.1 now. > > > > I tried exporting the "dpdk_nic_bind.py" script into my VM (running DPD= K > > 1.7.1) and tried to check the status. The emulated devices were shown a= s > > neither bound to kernel nor to IGB_UIO as evident from below output:- > > > > > <------------------------------------------------------------------------= ---------------------------> > > 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 > > > > > > 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:00:03.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Dig= b_uio > > > > Other network devices > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 0000:00:04.0 '82540EM Gigabit Ethernet Controller' unused=3Digb_uio > > 0000:00:05.0 '82540EM Gigabit Ethernet Controller' unused=3Digb_uio > > > <------------------------------------------------------------------------= ---------------------------> > > > > When i tried to forcefully bind the NICs using the "--bind=3Digb_uio" > option > > Was there any output of the dpdk_nic_bind script? What does the output of > it with --status show afterwards? > > =E2=80=8B [MANOJ]=E2=80=8B =E2=80=8BYes. Please refer below output:- ******************************************************************** 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:00:04.0 '82540EM Gigabit Ethernet Controller' drv=3Digb_uio unused=3D 0000:00:05.0 '82540EM Gigabit Ethernet Controller' drv=3Digb_uio 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:00:03.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Digb_ui= o Other network devices =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =E2=80=8B ******************************************************************** =E2=80=8BHowever, when i start the DPDK application, i am getting the error= log as indicated in earlier mail. =E2=80=8B The difference with DPDK 1.6.1 is that at the same stage IGB_UIO has already bound the assigned devices without having to explicitly run the "dpdk_nic_bind.py". Please find below the application log when run with DPDK 1.6.0:- =E2=80=8B******************************************************************= ** 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:00:04.0 '82540EM Gigabit Ethernet Controller' drv=3Digb_uio unused=3D 0000:00:08.0 '82540EM Gigabit Ethernet Controller' drv=3Digb_uio 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:00:03.0 'Virtio network device' if=3D drv=3Dvirtio-pci unused=3Digb_ui= o Other network devices =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ********************************************************************=E2=80= =8B =E2=80=8BKindly note that in both cases, logs have been taken after loading= IGB_UIO prior to starting DPDK application. =E2=80=8B =E2=80=8B[/MANOJ]=E2=80=8B Regards, > /Bruce > > =E2=80=8BRegards, MANOJ