On Fri, Jun 17, 2016 at 11:32:36AM -0400, Aaron Conole wrote:
> Prior to this commit, the only way to add a vhost-user socket to the
> system is by relying on librte_vhost to open the unix domain socket and
> add it to the unix socket list. This is problematic for applications
> which would like to set the permissions,
So, you want to address the issue raised by following patch?
http://dpdk.org/dev/patchwork/patch/12222/
I would still like to stick to my proposal, that is to introduce a
new API to do the permission change at anytime, if we end up with
wanting to introduce a new API.
> or applications which are not
> directly allowed to open sockets due to policy restrictions.
Could you name a specific example?
BTW, JFYI, since 16.07, DPDK supports client mode. It's QEMU (acting
as the server) will create the socket file. I guess that would diminish
(or even avoid?) the permission pain that DPDK acting as server brings.
I doubt the API to do the permission change is really needed then.
--yliu
