From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) by dpdk.org (Postfix) with ESMTP id C23DB156 for ; Wed, 13 Nov 2013 17:15:32 +0100 (CET) Received: by mail-lb0-f180.google.com with SMTP id u14so527756lbd.39 for ; Wed, 13 Nov 2013 08:16:28 -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=qCrINAKLvZF/VAACn+sG2fYOTOsMjmzaeeyFfQhvb98=; b=uSpGw8HWQSrmmUdgEeCA7z77b2tH0wZySBdnk/o4mBnShOD6MwcVBo/MBqPZe72Fe7 LNxdteYSbCMgm1kQ7HCoFWGFmUfcHQVFd+eP7brRPy2fCeMJ64vt4POY0a1skgmxHxBu VhC59V3S5xyVVFDaM5phnLcKzsV/Ok8hBGqksVT19pOBh5ufEc6JXT8fBuuNejB5PcvC bNxJ3yN28zrT1p16Pbg6sPqQOg830saCeurwWyHrrjxh94OUhJvarjjTVXhtXW3JKdhR WRUQ+RBgyXTplMK2mFgPe811EM5q30zMlglBdNVh40FHPISYtoFSjbhmDCkJwAehRmMA RB7Q== MIME-Version: 1.0 X-Received: by 10.152.22.131 with SMTP id d3mr2170937laf.35.1384359387859; Wed, 13 Nov 2013 08:16:27 -0800 (PST) Received: by 10.114.181.144 with HTTP; Wed, 13 Nov 2013 08:16:27 -0800 (PST) In-Reply-To: References: <20131105122319.GA26200@debian> <20131105160437.GK26200@debian> Date: Thu, 14 Nov 2013 00:16:27 +0800 Message-ID: From: Jose Gavine Cueto To: Jyotiswarup Raiturkar Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] pci_unbind.py failure 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: Wed, 13 Nov 2013 16:15:33 -0000 Hi Jyotiswarup, Based on my experience and little knowledge on the code, rte_pmd_init_all registers your poll-mode driver (em in this case) and sets the device initialization function. rte_eal_pci_probe will then probe for pci devices and then initialize their corresponding drivers. These initialization will increment the number of usable ports (e.g. e1000) and also the value that is returned by rte_eth_dev_count. I think that without calling rte_pmd_init_all, rte_eal_pci_probe will fail unless you have a specialize routine that sets the initialization function of your driver. Cheers, Pepe On Wed, Nov 13, 2013 at 11:00 PM, Jyotiswarup Raiturkar < jyotisr5@googlemail.com> wrote: > Hi all > > Hi > > I'm using vmware player , i've using ethernet1.virtualDev = "e1000" > > Yes I do rte_eal_init() and then rte_eal_pci_probe(). I'm not using > rte_pmd_init_all() ; not sure what it does.. Also FYI i'm using DPDK > 1.4.1r0 > > I've finally got real hardware too, will try on the same and update the > thread.. > > Regards > Jyoti > > > On Wed, Nov 13, 2013 at 8:27 PM, Vladimir Medvedkin >wrote: > > > Hi all, > > > > I have faced with similar problem on my real environment with 82599 nic. > > Looks like in some cases rte_eth_dev_count() return 0 instead of real > > number of igb_uio binded ports. After restarting app several times > > rte_eth_dev_count() return real number of ports and continue execute > > normaly. > > > > > > 2013/11/13 Daniel Kaminsky > > > > > Hi Jyotiswarup, > > > > > > Did you initialized all the relevant parts before > > > (rte_eal_init(), rte_pmd_init_all() and don't forget > > rte_eal_pci_probe())? > > > > > > Regards, > > > Daniel > > > > > > > > > On Wed, Nov 13, 2013 at 1:27 PM, Jose Gavine Cueto > > >wrote: > > > > > > > Hi, > > > > > > > > How are you using it? I've successfully used it with vbox. > > > > > > > > Cheers > > > > On Nov 13, 2013 7:17 PM, "Jyotiswarup Raiturkar" < > > > jyotisr5@googlemail.com> > > > > wrote: > > > > > > > > > hi > > > > > > > > > > I got my application running inside a vm (vmplayer) where the VM > > > > emulates a > > > > > e1000 NIC (82545EM). But rte_eth_dev_count() seems to return 0.. > From > > > the > > > > > website looks like it's a supported NIC . My lspci and pci_ubind > > status > > > > is > > > > > below. Any pointers? > > > > > > > > > > # ./tools/pci_unbind.py --status > > > > > > > > > > Network devices using IGB_UIO driver > > > > > ==================================== > > > > > 0000:02:06.0 '82545EM Gigabit Ethernet Controller (Copper)' > > drv=igb_uio > > > > > unused=e1000 > > > > > > > > > > Network devices using kernel driver > > > > > =================================== > > > > > 0000:02:01.0 '79c970 [PCnet32 LANCE]' if=eth1 drv=pcnet32 unused= > > > > *Active* > > > > > > > > > > Other network devices > > > > > ===================== > > > > > > > > > > > > > > > > > > > > # lspci -vt > > > > > -[0000:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX > Host > > > > > bridge > > > > > +-01.0-[01]-- > > > > > +-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA > > > > > +-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE > > > > > +-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI > > > > > +-07.7 VMware Virtual Machine Communication Interface > > > > > +-0f.0 VMware SVGA II Adapter > > > > > +-10.0 LSI Logic / Symbios Logic 53c1030 PCI-X > Fusion-MPT > > > > Dual > > > > > Ultra320 SCSI > > > > > +-11.0-[02]--+-00.0 VMware USB1.1 UHCI Controller > > > > > | +-01.0 Advanced Micro Devices [AMD] 79c970 > > > > > [PCnet32 LANCE] > > > > > | +-02.0 Ensoniq ES1371 [AudioPCI-97] > > > > > | +-03.0 VMware USB2 EHCI Controller > > > > > | +-05.0 VMware Device 07e0 > > > > > | \-06.0 Intel Corporation 82545EM Gigabit > > > > Ethernet > > > > > Controller (Copper) > > > > > +-15.0-[03]-- > > > > > +-15.1-[04]-- > > > > > +-15.2-[05]-- > > > > > +-15.3-[06]-- > > > > > +-15.4-[07]-- > > > > > +-15.5-[08]-- > > > > > +-15.6-[09]-- > > > > > +-15.7-[0a]-- > > > > > +-16.0-[0b]-- > > > > > +-16.1-[0c]-- > > > > > +-16.2-[0d]-- > > > > > +-16.3-[0e]-- > > > > > +-16.4-[0f]-- > > > > > +-16.5-[10]-- > > > > > +-16.6-[11]-- > > > > > +-16.7-[12]-- > > > > > +-17.0-[13]-- > > > > > +-17.1-[14]-- > > > > > +-17.2-[15]-- > > > > > +-17.3-[16]-- > > > > > +-17.4-[17]-- > > > > > +-17.5-[18]-- > > > > > +-17.6-[19]-- > > > > > +-17.7-[1a]-- > > > > > +-18.0-[1b]-- > > > > > +-18.1-[1c]-- > > > > > +-18.2-[1d]-- > > > > > +-18.3-[1e]-- > > > > > +-18.4-[1f]-- > > > > > +-18.5-[20]-- > > > > > +-18.6-[21]-- > > > > > \-18.7-[22]-- > > > > > > > > > > > > > > > Regards > > > > > Jyotiswarup > > > > > > > > > > > > > > > On Tue, Nov 5, 2013 at 9:34 PM, Cyril Cressent < > > > cyril.cressent@intel.com > > > > > >wrote: > > > > > > > > > > > On Tue, Nov 05, 2013 at 08:01:06PM +0530, Jyotiswarup Raiturkar > > > wrote: > > > > > > > > > > > > > Thanks for the quick reply. I saw some definitions of > > > e1000_phy_82579 > > > > > > hence > > > > > > > I thought (hoped) the NIC would be supported. I will try to run > > my > > > > dpdk > > > > > > app > > > > > > > inside a VM with an emulated e1000 NIC (just to test the code > > ..). > > > > > > > > > > > > As a general rule, even if you find references to a NIC in the > poll > > > > mode > > > > > > drivers, if it's not listed in > > > > > > lib/librte_eal/common/include/rte_pci_dev_ids.h > > > > > > then consider the NIC as not supported. > > > > > > > > > > > > Good luck with the VM, > > > > > > > > > > > > Cyril > > > > > > > > > > > > > > > > > > > > > -- To stop learning is like to stop loving.