[dpdk-dev] pci_unbind.py failure

2013-11-14 Thread Jose Gavine Cueto
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 initia

[dpdk-dev] pci_unbind.py failure

2013-11-13 Thread Jyotiswarup Raiturkar
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

[dpdk-dev] pci_unbind.py failure

2013-11-13 Thread Jose Gavine Cueto
Hi, How are you using it? I've successfully used it with vbox. Cheers On Nov 13, 2013 7:17 PM, "Jyotiswarup Raiturkar" 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 > websit

[dpdk-dev] pci_unbind.py failure

2013-11-13 Thread Vladimir Medvedkin
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.

[dpdk-dev] pci_unbind.py failure

2013-11-13 Thread Jyotiswarup Raiturkar
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 device

[dpdk-dev] pci_unbind.py failure

2013-11-13 Thread 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

[dpdk-dev] pci_unbind.py failure

2013-11-05 Thread Jyotiswarup Raiturkar
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 wrote: > On Tue, No

[dpdk-dev] pci_unbind.py failure

2013-11-05 Thread Jyotiswarup Raiturkar
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 Network devices using kernel driver ==

[dpdk-dev] pci_unbind.py failure

2013-11-05 Thread Cyril Cressent
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 ..). A

[dpdk-dev] pci_unbind.py failure

2013-11-05 Thread Cyril Cressent
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