On 05/26/2017 03:12 PM, Stephen Finucane wrote: > Apparently dpdkvhostuser interfaces are inferior to dpdkvhostuserclient. > Explain why. > > Signed-off-by: Stephen Finucane <step...@that.guru> > Cc: Ciara Loftus <ciara.lof...@intel.com> > Cc: Kevin Traynor <ktray...@redhat.com> > --- > I'd like to note what happens to traffic when OVS or a VM is restarted > for both port types. If someone knows the answer to this, please feel > free to take ownership of that patch/ask me for a v2. > --- > Documentation/topics/dpdk/vhost-user.rst | 8 ++++++-- > 1 file changed, 6 insertions(+), 2 deletions(-) > > diff --git a/Documentation/topics/dpdk/vhost-user.rst > b/Documentation/topics/dpdk/vhost-user.rst > index ba22684..2e2396b 100644 > --- a/Documentation/topics/dpdk/vhost-user.rst > +++ b/Documentation/topics/dpdk/vhost-user.rst > @@ -54,8 +54,12 @@ vHost User sockets, and the client connects to the server. > Depending on which > port type you use, ``dpdkvhostuser`` or ``dpdkvhostuserclient``, a different > configuration of the client-server model is used. > > -For vhost-user ports, Open vSwitch acts as the server and QEMU the client. > For > -vhost-user-client ports, Open vSwitch acts as the client and QEMU the server. > +For vhost-user ports, Open vSwitch acts as the server and QEMU the client. > This > +means if OVS dies, all VMs **must** be restarted. On the other hand, for > +vhost-user-client ports, OVS acts as the client and QEMU the server. This > means > +OVS can die and be restarted without issue, and it is also possible to > restart > +an instance itself. For this reason, vhost-user-client ports are the > preferred > +type for most use cases. > > .. _dpdk-vhost-user: > > LGTM. Acked-by: Kevin Traynor <ktray...@redhat.com> _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev