Re: [ovs-dev] [PATCH v2 0/2] vhost-user: Add the ability to control ownership/permissions

2016-07-20 Thread Aaron Conole
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

Re: [ovs-dev] [PATCH v2 0/2] vhost-user: Add the ability to control ownership/permissions

2016-06-02 Thread Ansis Atteka
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

Re: [ovs-dev] [PATCH v2 0/2] vhost-user: Add the ability to control ownership/permissions

2016-06-01 Thread Aaron Conole
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

Re: [ovs-dev] [PATCH v2 0/2] vhost-user: Add the ability to control ownership/permissions

2016-06-01 Thread Ansis Atteka
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

Re: [ovs-dev] [PATCH v2 0/2] vhost-user: Add the ability to control ownership/permissions

2016-05-23 Thread Aaron Conole
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

Re: [ovs-dev] [PATCH v2 0/2] vhost-user: Add the ability to control ownership/permissions

2016-05-23 Thread Christian Ehrhardt
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

[ovs-dev] [PATCH v2 0/2] vhost-user: Add the ability to control ownership/permissions

2016-05-20 Thread Aaron Conole
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