From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Aaron Conole <aconole@redhat.com>
Cc: dev@dpdk.org, Huawei Xie <huawei.xie@intel.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-dev] [RFC] librte_vhost: Add unix domain socket fd registration
Date: Tue, 21 Jun 2016 15:21:28 +0800 [thread overview]
Message-ID: <20160621072128.GK23111@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1466177556-14891-1-git-send-email-aconole@redhat.com>
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
next prev parent reply other threads:[~2016-06-21 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 15:32 Aaron Conole
2016-06-21 7:21 ` Yuanhan Liu [this message]
2016-06-21 13:15 ` Aaron Conole
2016-06-24 2:31 ` Yuanhan Liu
2016-06-24 7:43 ` Loftus, Ciara
2016-06-24 7:51 ` Yuanhan Liu
2016-06-24 12:23 ` Aaron Conole
2016-06-27 11:53 ` Yuanhan Liu
2016-06-27 19:19 ` Aaron Conole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160621072128.GK23111@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=aconole@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).