[dpdk-dev] Vmxnet3 pmd
Patel, Rashmin N
rashmin.n.patel at intel.com
Wed Aug 13 18:58:10 CEST 2014
This is known issue with dev_stop of vmxnet3_pmd. Vmxnet3_cmd_ring_release() routine calls rte_free(ring->buf_info), which should be reused instead. Because it's not being reallocated at dev_start, otherwise reallocation is needed. I've a patch that works for me, I'll submit it after some testing.
From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Alex Markuze
Sent: Wednesday, August 13, 2014 3:14 AM
To: dev at dpdk.org
Subject: [dpdk-dev] Vmxnet3 pmd
Hi, I Have a simple dpdk app - basically a KNI interface with the dpdk layer serving only as a pipeline.
This allows me to ping between vEth0 on different VM's works great with ixgbevf.
Now I moved to ESXi5.5 , Ubuntu14.4 VM (Dpdk 1.7).
When running the same code* I've discovered that the polling doesn't retrieve any packets after vEth0 gents an IP. I've resolved this issue by removing the dev restart calls I had in the callback.
// ret = rte_eth_dev_start(port_id);
Is this a know issue? how can I report a BUG if its not.
*Except this line I needed to add to setup the TXQ.
tx_conf.txq_flags |= (ETH_TXQ_FLAGS_NOMULTSEGS | ETH_TXQ_FLAGS_NOOFFLOADS);
More information about the dev