Aaron Conole writes:
> Currently, when using Open vSwitch with DPDK and qemu guests, the recommended
> method for joining the guests is via the dpdkvhostuser interface. This
> interface uses Unix Domain sockets to communicate. When these sockets are
> created, they inherit
On 1 June 2016 at 12:51, Aaron Conole wrote:
> Ansis Atteka writes:
>
> > On 20 May 2016 at 13:32, Aaron Conole wrote:
> >
> >> Currently, when using Open vSwitch with DPDK and qemu guests, the
> >> recommended
> >> method for
Ansis Atteka writes:
> On 20 May 2016 at 13:32, Aaron Conole wrote:
>
>> Currently, when using Open vSwitch with DPDK and qemu guests, the
>> recommended
>> method for joining the guests is via the dpdkvhostuser interface. This
>> interface uses Unix
On 20 May 2016 at 13:32, Aaron Conole wrote:
> Currently, when using Open vSwitch with DPDK and qemu guests, the
> recommended
> method for joining the guests is via the dpdkvhostuser interface. This
> interface uses Unix Domain sockets to communicate. When these sockets are
Christian Ehrhardt writes:
> Hi Aaron,
> not on this revision, but I tested and liked your series quite a lot when
> it was still younger :-).
> While I still think a long term solution should be in DPDK itself - as you
> have seen the discussion there tended to
Hi Aaron,
not on this revision, but I tested and liked your series quite a lot when
it was still younger :-).
While I still think a long term solution should be in DPDK itself - as you
have seen the discussion there tended to add an extra API.
That can take a while plus the adoption in consuming
Currently, when using Open vSwitch with DPDK and qemu guests, the recommended
method for joining the guests is via the dpdkvhostuser interface. This
interface uses Unix Domain sockets to communicate. When these sockets are
created, they inherit the permissions and ownership from the vswitchd