search for: opendataplan

...s virtio-net. Discussion ---------- The result is that applications in separate VMs can communicate in true zero-copy fashion. 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. This is an idea I want to share but I'm not working on a prototype. Feel free to flesh it out further and try it! Open issues: * Multiple VMs? * Multiqueue? * Choice of shared buffer allocation algorithm? * etc Stefan -------------- next part ---...

...s virtio-net. Discussion ---------- The result is that applications in separate VMs can communicate in true zero-copy fashion. 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. This is an idea I want to share but I'm not working on a prototype. Feel free to flesh it out further and try it! Open issues: * Multiple VMs? * Multiqueue? * Choice of shared buffer allocation algorithm? * etc Stefan -------------- next part ---...

...ult is that applications in separate VMs can communicate in true >> zero-copy fashion. >> >> 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. >> >> This is an idea I want to share but I'm not working on a prototype. >> Feel free to flesh it out further and try it! > > Definetly interesting. It seems you get much of the needed > infrastructure by simply leve...

...ult is that applications in separate VMs can communicate in true >> zero-copy fashion. >> >> 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. >> >> This is an idea I want to share but I'm not working on a prototype. >> Feel free to flesh it out further and try it! > > Definetly interesting. It seems you get much of the needed > infrastructure by simply leve...

...may be necessary to remove virtio-dev at lists.oasis-open.org 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...

...------ > The result is that applications in separate VMs can communicate in true > zero-copy fashion. > > 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. > > This is an idea I want to share but I'm not working on a prototype. > Feel free to flesh it out further and try it! Definetly interesting. It seems you get much of the needed infrastructure by simply leveraging what PCI gives you any...