On Tue, Jan 27, 2015 at 10:35:40AM +0800, Ouyang Changchun wrote: > This is the patch set for single virtio implementation. > > Why we need single virtio? > ============================ > As we know currently there are at least 3 virtio PMD driver implementations: > A) lib/librte_pmd_virtio(refer as virtio A); > B) virtio_net_pmd by 6wind(refer as virtio B); > C) virtio by Brocade/vyatta(refer as virtio C); > > Integrating 3 implementations into one could reduce the maintaining cost and > time, > in other hand, user don't need practice their application on 3 variant one by > one to see > which one is the best for them;
Thank you so much for this, using virtio drivers in DPDK has been messy and unpleasant in the past, and you clearly wrote a lot of nice new code to help improve it all. Previously I'd reported a bug, where all RTE virtio drivers I tried (A and B, because I did not know C existed), failed to work with the virtio-net interfaces exposed in VirtualBox, due to various strange errors, and they all only worked with the virtio-net interfaces from qemu. I wanted to find out if we managed to fix this other problem, because I would really like to use the Vagrant VM deployment tool (https://www.vagrantup.com/) to distribute my open-source DPDK based application to everyone in the open source community. The better the out-of-box experience of practical community-created DPDK-based real-life example applications similar to mine, the more adoption of DPDK and better DPDK community we will be able to have as time marches forward. If we could manage to get it to work in VirtualBox, then I could surely help do some app-level testing on the new code, if we could see it in a test branch or test repo somewhere I could access it. Sincerely, Matthew Hall