I've encountered a couple scenarios with vmxnet3 (dpdk 2.2 and 16.07) that look pretty much identical to this: http://dpdk.org/ml/archives/users/2016-October/001063.html
Do we have a maintainer for the vmxnet3 driver? I tried emailing the one listing in the MAINTAINERS file but the mail bounced. Is anyone familiar with the issue described in the thread above? Thanks, Dave
