[dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015
Matthew Hall
mhall at mhcomputing.net
Wed Oct 22 21:22:19 CEST 2014
On Wed, Oct 22, 2014 at 01:48:36PM +0000, O'driscoll, Tim wrote:
> Single Virtio Driver: Merge existing Virtio drivers into a single
> implementation, incorporating the best features from each of the existing
> drivers.
Tim,
There is a lot of good stuff in there.
Specifically, in the virtio-net case above, I have discovered, and Sergio at
Intel just reproduced today, that neither virtio PMD works at all inside of
VirtualBox. One can't init, and the other gets into an infinite loop. But yet
it's claiming support for VBox on the DPDK Supported NICs page though it
doesn't seem it ever could have worked.
So I'd like to request an initiative alongside any virtio-net and/or vmxnet3
type of changes, to make some kind of a Virtualization Test Lab, where we
support VMWare ESXi, QEMU, Xen, VBox, and the other popular VM systems.
Otherwise it's hard for us community / app developers to make the DPDK
available to end users in simple, elegant ways, such as packaging it into
Vagrant VM's, Amazon AMI's etc. which are prebaked and ready-to-run.
Note personally of course I prefer using things like the 82599... but these
are only going to be present after the customers have begun to adopt and test
in the virtual environment, then they decide they like it and want to scale up
to bigger boxes.
Another thing which would help in this area would be additional improvements
to the NUMA / socket / core / number of NICs / number of queues
autodetections. To write a single app which can run on a virtual card, a
hardware card without RSS available, and a hardware card with RSS available,
in a thread-safe, flow-safe way, is somewhat complex at the present time.
I'm running into this in the VM based environments because most VNIC's don't
have RSS and it complicates the process of keeping consistent state of the
flows among the cores.
Thanks,
Matthew.
More information about the dev
mailing list