2016-04-25 21:16, Yuanhan Liu: > On Mon, Apr 25, 2016 at 11:18:16AM +0200, Christian Ehrhardt wrote: > > The API doesn't hold a way to specify a owner/permission set for vhost_user > > created sockets. > > Yes, it's kind of like a known issue. So, thanks for bringing it, with > a solution, for dicussion (cc'ed more people). [...] > > But I'd be interested if DPDK in general would be interested in: > > a) an approach like this? > > You were trying to add a vhost specific stuff as EAL command option, > which is something we might should try to avoid.
Yes, -1 > > b) would prefer a change of the API? > > Adding a new option to the current register API might will not work well, > either. It gives you no ability to do a dynamic change later. I mean, > taking OVS as an example, OVS provides you the flexible ability to do all > kinds of configuration in a dynamic way, say number of rx queues. If we > do the permissions setup in the register time, there would be no way to > change it later, right? > > So, I'm thinking that we may could add a new API for that? It then would > allow applications to change it at anytime. A vhost API in the library? And for vhost PMD? What about devargs parameters? > > c) consider it an issue of consuming projects and let them take care? > > It's not exactly an issue of consuming projects; we created the socket > file after all. Yes