On 1 September 2014 09:10, loy wolfe loywo...@gmail.com wrote:
If the neutron side MD is just for snabbswitch, then I thinks there is no
change to be merged into the tree. Maybe we can learn from sriov nic,
although backend is vendor specific, but the MD is generic, can support
snabb,
If the neutron side MD is just for snabbswitch, then I thinks there is no
change to be merged into the tree. Maybe we can learn from sriov nic,
although backend is vendor specific, but the MD is generic, can support
snabb, dpdkovs, ans other userspace vswitch, etc.
As the reference implementation
On 8/30/2014 11:22 PM, Ian Wells wrote:
The problem here is that you've removed the vif_driver option and now
you're preventing the inclusion of named VIF types into the generic
driver, which means that rather than adding a package to an
installation to add support for a VIF driver it's now
Howdy!
I am writing to ask whether it will be possible to merge VIF_VHOSTUSER [1]
in Juno?
VIF_VHOSTUSER adds support for a QEMU 2.1 has a feature called vhost-user
[2] that allows a guest to do Virtio-net I/O via a userspace vswitch. This
makes it convenient to deploy new vswitches that are
On Wed, Aug 27, 2014 at 04:06:25PM +0200, Luke Gorrie wrote:
Howdy!
I am writing to ask whether it will be possible to merge VIF_VHOSTUSER [1]
in Juno?
VIF_VHOSTUSER adds support for a QEMU 2.1 has a feature called vhost-user
[2] that allows a guest to do Virtio-net I/O via a userspace
