[dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x?
Prashant,
I was also able to hit the issue your hitting using Esxi
5.1.0 evaluation and Fedora 20 X86_64 guest. I was able to fix the
issue by setting CONFIG_RTE_EAL_UNBIND_PORTS=y option in
defconfig_x86_64-default-linuxapp-gcc configuration file.
Issue seen
EAL: PCI device :03:00.0 on NUMA socket -1
EAL: probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL: Device is blacklisted, not initializing
EAL: PCI device :0b:00.0 on NUMA socket -1
EAL: probe driver: 15ad:7b0 rte_vmxnet3_pmd
Program received signal SIGSEGV, Segmentation fault.
eth_vmxnet3_dev_init (eth_drv=, eth_dev=0x754480
) at
/root/source/dpdk-1.6.0r1/lib/librte_pmd_vmxnet3/vmxnet3_ethdev.c:218
218 ver = VMXNET3_READ_BAR1_REG(hw, VMXNET3_REG_VRRS);
Missing separate debuginfos, use: debuginfo-install glibc-2.18-11.fc20.x86_64
(gdb) p hw
$1 = (struct vmxnet3_hw *) 0x7fffd8fc1040
(gdb) p *hw
$2 = {hw_addr0 = 0x0, hw_addr1 = 0x0, back = 0x0, device_id = 1968,
vendor_id = 5549, subsystem_device_id = 0, subsystem_vendor_id = 0,
adapter_stopped = 0, perm_addr = "\000\000\000\000\000",
num_tx_queues = 1 '\001', num_rx_queues = 1 '\001', bufs_per_pkt = 1
'\001', cur_mtu = 0,
tqd_start = 0x0, rqd_start = 0x0, shared = 0x0, sharedPA = 0,
queueDescPA = 0, queue_desc_len = 0, rss_conf = 0x0, rss_confPA = 0,
mf_table = 0x0}
(gdb)
#define VMXNET3_PCI_BAR1_REG_ADDR(hw, reg) \
((volatile uint32_t *)((char *)(hw)->hw_addr1 + (reg)))
#define VMXNET3_READ_BAR1_REG(hw, reg) \
vmxnet3_read_addr(VMXNET3_PCI_BAR1_REG_ADDR((hw), (reg)))
lib/librte_pmd_vmxnet3/vmxnet3_ethdev.h
Issue not seen after enabling CONFIG_RTE_EAL_UNBIND_PORTS=y
==
[root at localhost build]# ./l2fwd -c 0xf -b :03:00.0 -n 1 -- -p 0x6
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Skip lcore 4 (not detected)
EAL: Skip lcore 5 (not detected)
EAL: Skip lcore 6 (not detected)
EAL: Skip lcore 7 (not detected)
EAL: Skip lcore 8 (not detected)
EAL: Skip lcore 9 (not detected)
EAL: Skip lcore 10 (not detected)
EAL: Skip lcore 11 (not detected)
EAL: Skip lcore 12 (not detected)
EAL: Skip lcore 13 (not detected)
EAL: Skip lcore 14 (not detected)
EAL: Skip lcore 15 (not detected)
EAL: Skip lcore 16 (not detected)
EAL: Skip lcore 17 (not detected)
EAL: Skip lcore 18 (not detected)
EAL: Skip lcore 19 (not detected)
EAL: Skip lcore 20 (not detected)
EAL: Skip lcore 21 (not detected)
EAL: Skip lcore 22 (not detected)
EAL: Skip lcore 23 (not detected)
EAL: Skip lcore 24 (not detected)
EAL: Skip lcore 25 (not detected)
EAL: Skip lcore 26 (not detected)
EAL: Skip lcore 27 (not detected)
EAL: Skip lcore 28 (not detected)
EAL: Skip lcore 29 (not detected)
EAL: Skip lcore 30 (not detected)
EAL: Skip lcore 31 (not detected)
EAL: Skip lcore 32 (not detected)
EAL: Skip lcore 33 (not detected)
EAL: Skip lcore 34 (not detected)
EAL: Skip lcore 35 (not detected)
EAL: Skip lcore 36 (not detected)
EAL: Skip lcore 37 (not detected)
EAL: Skip lcore 38 (not detected)
EAL: Skip lcore 39 (not detected)
EAL: Skip lcore 40 (not detected)
EAL: Skip lcore 41 (not detected)
EAL: Skip lcore 42 (not detected)
EAL: Skip lcore 43 (not detected)
EAL: Skip lcore 44 (not detected)
EAL: Skip lcore 45 (not detected)
EAL: Skip lcore 46 (not detected)
EAL: Skip lcore 47 (not detected)
EAL: Skip lcore 48 (not detected)
EAL: Skip lcore 49 (not detected)
EAL: Skip lcore 50 (not detected)
EAL: Skip lcore 51 (not detected)
EAL: Skip lcore 52 (not detected)
EAL: Skip lcore 53 (not detected)
EAL: Skip lcore 54 (not detected)
EAL: Skip lcore 55 (not detected)
EAL: Skip lcore 56 (not detected)
EAL: Skip lcore 57 (not detected)
EAL: Skip lcore 58 (not detected)
EAL: Skip lcore 59 (not detected)
EAL: Skip lcore 60 (not detected)
EAL: Skip lcore 61 (not detected)
EAL: Skip lcore 62 (not detected)
EAL: Skip lcore 63 (not detected)
EAL: Setting up memory...
EAL: Ask a virtual area of 0x20 bytes
EAL: Virtual area found at 0x7f3a76a0 (size = 0x20)
EAL: Ask a virtual area of 0x7c0 bytes
EAL: Virtual area found at 0x7f3a6ec0 (size = 0x7c0)
EAL: Ask a virtual area of 0x20 bytes
EAL: Virtual area found at 0x7f3a6e80 (size = 0x20)
EAL: Requesting 64 pages of size 2MB from socket 0
EAL: TSC frequency is ~220 KHz
EAL: Master core 0 is ready (tid=76cfe880)
EAL: Core 3 is ready (tid=6cffc700)
EAL: Core 1 is ready (tid=6dffe700)
EAL: Core 2 is ready (tid=6d7fd700)
EAL: PCI device :03:00.0 on NUMA socket -1
EAL: probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL: Device is blacklisted, not initializing
EAL: PCI device :0b:00.0 on NUMA socket -1
EAL: probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL: PCI memory mapped at 0x7f3a76d1
EAL: PCI memory mapped at 0x7f3a76d0f000
EAL: PCI memory mapped at 0x7f3a76d0d000
EAL: PCI device :13:00.0 on NUMA socket -1
EAL: probe driver: 15ad
[dpdk-dev] Intel 82571EB PMD support
Hi, Have checked this file too. It's listed and also init of pmd is fine and working since link is up. After sending the packets from directly connected interface, we are seeing that rx nic stats are increasing but We are not seeing descriptor done status ( E1000_RX_STAT_DD ) set hence it is not able to get the packet from rx software ring. Since the link is up, it should be able to receive the packets. Can anyone help resolve this issue? Thanks & Regards Chetan Bali From: Jayakumar, Muthurajan [muthurajan.jayaku...@intel.com] Sent: Saturday, March 08, 2014 9:52 PM To: Chetan Bali; dev at dpdk.org Subject: RE: Intel 82571EB PMD support Hi Chetan, 82571EB is supported - listed in http://dpdk.org/browse/dpdk/tree/lib/librte_eal/common/include/rte_pci_dev_ids.h Not heard issue before. RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_COPPER) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_FIBER) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES_DUAL) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_SERDES_QUAD) RTE_PCI_DEV_ID_DECL_EM(PCI_VENDOR_ID_INTEL, E1000_DEV_ID_82571EB_QUAD_COPPER) #define E1000_DEV_ID_82571EB_COPPER 0x105E #define E1000_DEV_ID_82571EB_FIBER0x105F #define E1000_DEV_ID_82571EB_SERDES 0x1060 #define E1000_DEV_ID_82571EB_SERDES_DUAL 0x10D9 #define E1000_DEV_ID_82571EB_SERDES_QUAD 0x10DA #define E1000_DEV_ID_82571EB_QUAD_COPPER 0x10A4 Thanks, -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Chetan Bali Sent: Saturday, March 08, 2014 4:58 AM To: dev at dpdk.org Subject: Re: [dpdk-dev] Intel 82571EB PMD support Hi, anyone faced the same issue before? Thanks & Regards Chetan Bali From: dev [dev-boun...@dpdk.org] On Behalf Of Chetan Bali Sent: Friday, March 07, 2014 3:48 PM To: dev at dpdk.org Subject: [dpdk-dev] Intel 82571EB PMD support Hi, Do we have PMD support for intel 82571EB. We are having e1000e driver supported for 82571EB in linux. DPDK Version : 1.6.0-r1 Linux Kernel : CentOS 6.4 [ kernel version 2.6.32-358.el6.x86_64 ] Issue: When we run DPDK example [ l2fwd ], we are able to see successful init of rte_pmd_em and link is also detected successfully. But the RX, TX count are zero. If we try to fetch nic stats using rte_eth_stats_get(), we can see around 256 ipacket count but after that error count [rx error ] starts increasing. We are not able to see any packet on user app [ l2fwd ]. Does anyone else face the same issue? Regards Chetan Bali === Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. === === Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. === === Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. ===
[dpdk-dev] Very low performance with l2fwd in a VM with PCI Passthrough
>To set up a VM and use the virtual functions from the 10G NIC, I suggest > referring to Chapter 9 of the Programmers Guide available at > http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/intel-dpdk- > programmers-guide.html . Instructions for setting up the VM to use VFs > are covered by section 9.2 Thanks a lot. This helped me out. Surya From: Richardson, Bruce Sent: Friday, March 7, 2014 1:27 AM To: Surya Nimmagadda; dev at dpdk.org Subject: RE: [dpdk-dev] Very low performance with l2fwd in a VM with PCI Passthrough > My setup details are > > - Traffic coming in on a 10G interface(eth0) and going out on another 10G > interface(eth1) > - Both 10G NICs are 82599 > - Created virtual functions eth5 and eth8 on eth0 and eth1 respectively > - eth5 and eth8 are mapped to eth0 and eth1 in a VM, with device type as > e1000 in Passthru mode. If the NIC in the VM is showing up as an e1000 then you have not passed the VF through to the VM at all, instead you are using an emulated NIC, which will be very, very slow in comparison - if nothing else, it's an emulated 1G NIC, not a 10G one. To set up a VM and use the virtual functions from the 10G NIC, I suggest referring to Chapter 9 of the Programmers Guide available at http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/intel-dpdk-programmers-guide.html . Instructions for setting up the VM to use VFs are covered by section 9.2
[dpdk-dev] Intel 82571EB PMD support
Chetan, I saw exactly that behavior with an 82599EB but running DPDK version 1.3.2 and CentOS 6.2 and the fix for me was upgrading to CentOS 6.4 - there was a thread a while back about a bug that caused DD to not be set but I can't seem to find it right now. I'm sorry I can't be of more help but at least this is a symptom that has been seen before. Regards, Stefan Sent from my smart phone; people don't make typos, Swype does! On Mar 7, 2014 5:18 AM, "Chetan Bali" wrote: > Hi, > > Do we have PMD support for intel 82571EB. We are having e1000e driver > supported for 82571EB in linux. > > DPDK Version : 1.6.0-r1 > > Linux Kernel : CentOS 6.4 [ kernel version 2.6.32-358.el6.x86_64 ] > > > Issue: > > When we run DPDK example [ l2fwd ], we are able to see successful init of > rte_pmd_em and link is also detected successfully. > But the RX, TX count are zero. If we try to fetch nic stats using > rte_eth_stats_get(), we can see around 256 ipacket count but after that > error count [rx error ] starts increasing. > > We are not able to see any packet on user app [ l2fwd ]. Does anyone else > face the same issue? > > Regards > Chetan Bali > > > > > > === > Please refer to http://www.aricent.com/legal/email_disclaimer.html > for important disclosures regarding this electronic communication. > > === >
[dpdk-dev] Intel 82571EB PMD support
Hi Stefan, It will be of great help if you or anyone else could help me resolve this issue. I have checked 82571EB on following setup: OS version: CentOS 6.4 [ kernel 2.6.32.358 ] DPDK version : DPDK 1.6.0-r1 Let me know if any update of centos can help resolve this issue? Thanks & Regards Chetan Bali From: Stefan Baranoff [sbaran...@gmail.com] Sent: Sunday, March 09, 2014 7:39 PM To: Chetan Bali Cc: dev at dpdk.org Subject: Re: [dpdk-dev] Intel 82571EB PMD support Chetan, I saw exactly that behavior with an 82599EB but running DPDK version 1.3.2 and CentOS 6.2 and the fix for me was upgrading to CentOS 6.4 - there was a thread a while back about a bug that caused DD to not be set but I can't seem to find it right now. I'm sorry I can't be of more help but at least this is a symptom that has been seen before. Regards, Stefan Sent from my smart phone; people don't make typos, Swype does! On Mar 7, 2014 5:18 AM, "Chetan Bali" mailto:chetan.bali at aricent.com>> wrote: Hi, Do we have PMD support for intel 82571EB. We are having e1000e driver supported for 82571EB in linux. DPDK Version : 1.6.0-r1 Linux Kernel : CentOS 6.4 [ kernel version 2.6.32-358.el6.x86_64 ] Issue: When we run DPDK example [ l2fwd ], we are able to see successful init of rte_pmd_em and link is also detected successfully. But the RX, TX count are zero. If we try to fetch nic stats using rte_eth_stats_get(), we can see around 256 ipacket count but after that error count [rx error ] starts increasing. We are not able to see any packet on user app [ l2fwd ]. Does anyone else face the same issue? Regards Chetan Bali === Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. === === Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. ===
