Hi Stefan,
Great topic. I am also extremely interested in helping Virtio-net become the standard for the networking industry (the universe of DPDK, etc).
On 22 April 2015 at 19:01, Stefan Hajnoczi <stefanha@xxxxxxxxxx> wrote:
[It may be necessary to remove virtio-dev@xxxxxxxxxxxxxxxxxxxx from CC
if you are a non-TC member.]
[Done.]
I think this approach could be fruitful in bringing virtio-net to
VM-to-VM networking use cases. Unless virtio-net is extended for this
use case, I'm afraid DPDK and OpenDataPlane communities might steer
clear of VIRTIO.
Questions:
- How fast is needed?
- How fast is the vhost-user support that shipped in DPDK 2.0?
- How fast would the new design likely be?
Our recent experience in Snabb Switch land is that networking on x86 is now more of a HPC problem than a system programming problem. The SIMD bandwidth per core keeps increasing that this erodes the value of traditional (and complex) system programming optimizations. I will be interested to compare notes with others on this, already on Haswell but more so when we have AVX512.
Incidentally, we also did a pile of work last year on zero-copy NIC->VM transfers and discovered a lot of interesting problems and edge cases where Virtio-net spec and/or drivers are hard to match up with common NICs. Happy to explain a bit about our experience if that would be valuable.
Cheers,
-Luke
_______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
