A new other_config DB option has been added called 'vhost-driver-mode'.
By default this is set to 'server' which is the mode of operation OVS
with DPDK has used up until this point - whereby OVS creates and manages
vHost user sockets.
If set to 'client', OVS will act as the vHost client and connec
The patch mostly looks good to me, thanks.
I'm not 100% sure about the interface. Can we make the flag interface
specific?
If I'm not mistaken we currently limit vhost-sock-dir to be under OVS
rundir. With client mode this is not necessary anymore.
I hope that client will be made the default m
>
> The patch mostly looks good to me, thanks.
> I'm not 100% sure about the interface. Can we make the flag interface
> specific?
I'm not 100% sure about making the flag interface specific :) Do you think
there's a use case for both client and server mode ports to be used in
conjunction with
2016-08-08 7:18 GMT-07:00 Loftus, Ciara :
> >
> > The patch mostly looks good to me, thanks.
> > I'm not 100% sure about the interface. Can we make the flag interface
> > specific?
>
> I'm not 100% sure about making the flag interface specific :) Do you think
> there's a use case for both client
>
>
> 2016-08-08 7:18 GMT-07:00 Loftus, Ciara :
> >
> > The patch mostly looks good to me, thanks.
> > I'm not 100% sure about the interface. Can we make the flag interface
> > specific?
>
> I'm not 100% sure about making the flag interface specific :) Do you think
> there's a use case for both
