From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by dpdk.org (Postfix) with ESMTP id D21CC7F0D for ; Tue, 11 Nov 2014 14:38:43 +0100 (CET) Received: by mail-ob0-f172.google.com with SMTP id wp4so7474867obc.3 for ; Tue, 11 Nov 2014 05:48:33 -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=KVb2eNivl4RJkbLVfWK5vYkvoGoP7xgPQufXOJatb7w=; b=yydsE9Ziz8yGZPfI3TKwRZBqnRCKP1iFpQh4oF2nci0BaeUGmA1YBVdRziWU9uMANU CwG2n9scjTRRn+hADcKV5DnMmohlout7I9sFxffAaKIPNWAdJFRWxEWglRH62wp7x35T v+KB8SVN4J+BwwpPc7J0BIengHE6rQwzJ/HC1ADNu3WAQ2KBTwJoC+Ym3LaIbmOTnnn8 R55YfVKNujOBOdVtQsQWH4DXcZzEaCoszuXjhT+RlIGm0m9DgO4/sAdrDVbDVSgMJsNv 34xfA0Q8M1TPpBp4anK2W8COMwOfiJ3dwa0vf2Xjwz1pZvY32pccQFXAmwhwczdhIW3x 75ug== MIME-Version: 1.0 X-Received: by 10.182.199.1 with SMTP id jg1mr1129424obc.73.1415713712939; Tue, 11 Nov 2014 05:48:32 -0800 (PST) Received: by 10.202.212.194 with HTTP; Tue, 11 Nov 2014 05:48:32 -0800 (PST) In-Reply-To: <20141110105802.GA7036@bricha3-MOBL3> References: <20141105101246.GA9856@bricha3-MOBL3> <20141107153053.GA10376@bricha3-MOBL3> <20141110105802.GA7036@bricha3-MOBL3> Date: Tue, 11 Nov 2014 19:18:32 +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: Tue, 11 Nov 2014 13:38:44 -0000 Bruce, Thanks for the input. Sure, will figure out the offending file behind this error and update this thread. Meanwhile, wanted to share one more observation regarding this issue: The "file descriptor error" is NOT SEEN with DPDK 1.7.0 (dpdk-1.7.0.tar.gz ) when explicitly binding NICs to IGB_UIO using the .py script. The issue is only seen when using DPDK 1.7.1 ( dpdk-1.7.1.tar.gz ). I hope the version i am using is the last official tag in the 1.7.x tree. I see that this problem ("file descriptor error") in DPDK 1.7.1 and its non-occurrence in DPDK 1.7.0 has already been reported in this group on Sep 11 by zimeiw in a mail with following subject line:- "*The= re are a lot of error log when run l3fwd of dpdk-1.7.1*". Couldn't find any responses to that thread. Regards, Manoj On Mon, Nov 10, 2014 at 4:28 PM, Bruce Richardson < bruce.richardson@intel.com> wrote: > On Fri, Nov 07, 2014 at 11:26:08PM +0530, Manoj Viswanath wrote: > > Hi Bruce, > > > > Please find my comment in lined. > > > > On Fri, Nov 7, 2014 at 9:00 PM, Bruce Richardson < > bruce.richardson@intel.com > > > 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 > application > > > > 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 > DPDK > > > > 1.7.1) and tried to check the status. The emulated devices were > shown as > > > > 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=3Digb_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_ui= o" > > > option > > > > > > Was there any output of the dpdk_nic_bind script? What does the outpu= t > 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=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 > > =E2=80=8B > > ******************************************************************** > > > > =E2=80=8BHowever, when i start the DPDK application, i am getting the e= rror 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=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 > > > > ********************************************************************=E2= =80=8B > > > > =E2=80=8BKindly note that in both cases, logs have been taken after loa= ding > IGB_UIO > > prior to starting DPDK application. =E2=80=8B > > > > =E2=80=8B[/MANOJ]=E2=80=8B > > > > Regards, > > Ok, so it appears that after running dpdk_nic_bind to bind the devices to > igb_uio > the differences between 1.6 and 1.7 are resolved for that part. The reaso= n > why you explicitly need to bind the devices in 1.7 is due to this commit > which > removes the pci id table from the igb_uio driver. > > > http://dpdk.org/browse/dpdk/commit/?id=3D629395b063e8278a05ea41908d1152fa= 68df098c > > As for the other errors you are seeing, I'm not sure of the cause, though > they > may be related to interrupt support for changes in link status. Can you > perhaps > use a debugger and find out what the file descriptor in question refers t= o? > > /Bruce >