* [dpdk-dev] pci_unbind.py failure
@ 2013-11-05 12:11 Jyotiswarup Raiturkar
2013-11-05 12:23 ` Cyril Cressent
0 siblings, 1 reply; 10+ messages in thread
From: Jyotiswarup Raiturkar @ 2013-11-05 12:11 UTC (permalink / raw)
To: dev
Hello
I'm trying to install DPDK on my laptop.
I have 82579LM NIC which i'm trying to bind to the igb_uio driver. I get
the following error
# ./tools/pci_unbind.py --status
Network devices using IGB_UIO driver
====================================
<none>
Network devices using kernel driver
===================================
0000:00:19.0 '82579LM Gigabit Network Connection' if=eth0 drv=e1000e
unused=
Other network devices
=====================
<none>
# ./tools/pci_unbind.py --force --bind=igb_uio 00:19.0
Error: bind failed for 0000:00:19.0 - Cannot bind to driver igb_uio
Error: unbind failed for 0000:00:19.0 - Cannot open
/sys/bus/pci/drivers//unbind
After this, the --status shows this :
# ./tools/pci_unbind.py --status
Network devices using IGB_UIO driver
====================================
<none>
Network devices using kernel driver
===================================
<none>
Other network devices
=====================
0000:00:19.0 '82579LM Gigabit Network Connection' unused=e1000e
My kernel version is 3.5.0-23-generic ( Ubuntu 12.04.2 LTS). I heard about
an UIO bug in 3.10; is this the same bug i;m hitting?
Thanks
Jyoti
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-05 12:11 [dpdk-dev] pci_unbind.py failure Jyotiswarup Raiturkar
@ 2013-11-05 12:23 ` Cyril Cressent
2013-11-05 14:31 ` Jyotiswarup Raiturkar
0 siblings, 1 reply; 10+ messages in thread
From: Cyril Cressent @ 2013-11-05 12:23 UTC (permalink / raw)
To: Jyotiswarup Raiturkar; +Cc: dev
On Tue, Nov 05, 2013 at 05:41:17PM +0530, Jyotiswarup Raiturkar wrote:
>
> I have 82579LM NIC which i'm trying to bind to the igb_uio driver. I get
> the following error
I can't find the 82579LM listed on
http://dpdk.org/doc/nics
or in
lib/librte_eal/common/include/rte_pci_dev_ids.h
My guess is that your NIC is not supported.
> My kernel version is 3.5.0-23-generic ( Ubuntu 12.04.2 LTS). I heard about
> an UIO bug in 3.10; is this the same bug i;m hitting?
No, the bug you mention prevented the correct registration of the second
and subsequent ports bound to igb_uio. The first port bound to igb_uio
was working fine.
Cyril
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-05 12:23 ` Cyril Cressent
@ 2013-11-05 14:31 ` Jyotiswarup Raiturkar
2013-11-05 16:04 ` Cyril Cressent
0 siblings, 1 reply; 10+ messages in thread
From: Jyotiswarup Raiturkar @ 2013-11-05 14:31 UTC (permalink / raw)
To: Jyotiswarup Raiturkar, dev
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 ..).
Thanks
On Tue, Nov 5, 2013 at 5:53 PM, Cyril Cressent <cyril.cressent@intel.com>wrote:
> On Tue, Nov 05, 2013 at 05:41:17PM +0530, Jyotiswarup Raiturkar wrote:
> >
> > I have 82579LM NIC which i'm trying to bind to the igb_uio driver. I get
> > the following error
>
> I can't find the 82579LM listed on
> http://dpdk.org/doc/nics
> or in
> lib/librte_eal/common/include/rte_pci_dev_ids.h
>
> My guess is that your NIC is not supported.
>
> > My kernel version is 3.5.0-23-generic ( Ubuntu 12.04.2 LTS). I heard
> about
> > an UIO bug in 3.10; is this the same bug i;m hitting?
>
> No, the bug you mention prevented the correct registration of the second
> and subsequent ports bound to igb_uio. The first port bound to igb_uio
> was working fine.
>
> Cyril
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-05 14:31 ` Jyotiswarup Raiturkar
@ 2013-11-05 16:04 ` Cyril Cressent
2013-11-13 11:17 ` Jyotiswarup Raiturkar
0 siblings, 1 reply; 10+ messages in thread
From: Cyril Cressent @ 2013-11-05 16:04 UTC (permalink / raw)
To: Jyotiswarup Raiturkar; +Cc: dev
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-05 16:04 ` Cyril Cressent
@ 2013-11-13 11:17 ` Jyotiswarup Raiturkar
2013-11-13 11:27 ` Jose Gavine Cueto
0 siblings, 1 reply; 10+ messages in thread
From: Jyotiswarup Raiturkar @ 2013-11-13 11:17 UTC (permalink / raw)
To: Jyotiswarup Raiturkar, dev
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
=====================
<none>
# 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
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-13 11:17 ` Jyotiswarup Raiturkar
@ 2013-11-13 11:27 ` Jose Gavine Cueto
2013-11-13 11:36 ` Daniel Kaminsky
0 siblings, 1 reply; 10+ messages in thread
From: Jose Gavine Cueto @ 2013-11-13 11:27 UTC (permalink / raw)
To: Jyotiswarup Raiturkar; +Cc: dev
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
> =====================
> <none>
>
>
> # 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
> >
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-13 11:27 ` Jose Gavine Cueto
@ 2013-11-13 11:36 ` Daniel Kaminsky
2013-11-13 14:57 ` Vladimir Medvedkin
0 siblings, 1 reply; 10+ messages in thread
From: Daniel Kaminsky @ 2013-11-13 11:36 UTC (permalink / raw)
To: Jose Gavine Cueto; +Cc: dev
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 <pepedocs@gmail.com>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
> > =====================
> > <none>
> >
> >
> > # 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
> > >
> >
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-13 11:36 ` Daniel Kaminsky
@ 2013-11-13 14:57 ` Vladimir Medvedkin
2013-11-13 15:00 ` Jyotiswarup Raiturkar
0 siblings, 1 reply; 10+ messages in thread
From: Vladimir Medvedkin @ 2013-11-13 14:57 UTC (permalink / raw)
To: Daniel Kaminsky; +Cc: dev
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 <daniel.kaminsky@infinitelocality.com>
> 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 <pepedocs@gmail.com
> >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
> > > =====================
> > > <none>
> > >
> > >
> > > # 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
> > > >
> > >
> >
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-13 14:57 ` Vladimir Medvedkin
@ 2013-11-13 15:00 ` Jyotiswarup Raiturkar
2013-11-13 16:16 ` Jose Gavine Cueto
0 siblings, 1 reply; 10+ messages in thread
From: Jyotiswarup Raiturkar @ 2013-11-13 15:00 UTC (permalink / raw)
To: Vladimir Medvedkin; +Cc: dev
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 <medvedkinv@gmail.com>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 <daniel.kaminsky@infinitelocality.com>
>
> > 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 <pepedocs@gmail.com
> > >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
> > > > =====================
> > > > <none>
> > > >
> > > >
> > > > # 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
> > > > >
> > > >
> > >
> >
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [dpdk-dev] pci_unbind.py failure
2013-11-13 15:00 ` Jyotiswarup Raiturkar
@ 2013-11-13 16:16 ` Jose Gavine Cueto
0 siblings, 0 replies; 10+ messages in thread
From: Jose Gavine Cueto @ 2013-11-13 16:16 UTC (permalink / raw)
To: Jyotiswarup Raiturkar; +Cc: dev
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 <medvedkinv@gmail.com
> >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 <daniel.kaminsky@infinitelocality.com>
> >
> > > 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 <pepedocs@gmail.com
> > > >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
> > > > > =====================
> > > > > <none>
> > > > >
> > > > >
> > > > > # 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.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-11-13 16:15 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-05 12:11 [dpdk-dev] pci_unbind.py failure Jyotiswarup Raiturkar
2013-11-05 12:23 ` Cyril Cressent
2013-11-05 14:31 ` Jyotiswarup Raiturkar
2013-11-05 16:04 ` Cyril Cressent
2013-11-13 11:17 ` Jyotiswarup Raiturkar
2013-11-13 11:27 ` Jose Gavine Cueto
2013-11-13 11:36 ` Daniel Kaminsky
2013-11-13 14:57 ` Vladimir Medvedkin
2013-11-13 15:00 ` Jyotiswarup Raiturkar
2013-11-13 16:16 ` Jose Gavine Cueto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).