That's correct. If you're using dpdk packaged vmxnet3 pmd, you should be able to bind it to igb_uio in Guest OS and start l2fwd/ l3fwd app in VM.
On the ESXi part, your vmxnet3 device must be connected to one of the vSwitches with Uplink port, so you don't need to configure anything else, I believe. Just make sure the packets coming in the Uplink port carries your vmxnet3 device's mac-vlan and they'll hit your device and the VM, ultimately ending up in your dpdk thread polling on vmxnet3 device in your app. Thanks, Rashmin On Jun 24, 2015 9:54 PM, Puneet Singh <singh1989p at gmail.com> wrote: I am migrating from using DPDK1.6r2 and the external vmxnet3 user map driver to DPDK2.0. I believe with DPDK2.0, the vmxnet3 PMD is builtin and I don?t need to use the external driver. I have been able to build the DPDK2.0 and I see that CONFIG_RTE_LIBRTE_VMXNET3_PMD is set to y in the config. Question is, what should be the steps that I follow on the ESXi node in my virtual machine to detect the NIC with the above driver (I do have vmxnet3 NIC there) Should I load the uio and take over the NIC the usual way with igb_uio and then run my application or are there any other steps to be followed. Regards -Puneet
