DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: 陈亚辉-云杉研发部 <goodluckwillcomesoon@gmail.com>,
	dev@dpdk.org, jiping@yunshan.net, xiangyang@yunshan.net,
	"David Marchand" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] eal: can not run secondary process on openstack environment
Date: Thu, 30 Apr 2020 09:09:02 -0700	[thread overview]
Message-ID: <20200430090902.0add5a96@hermes.lan> (raw)
In-Reply-To: <42a59c31-ccd4-f7b2-a1c2-e0ff20921145@intel.com>

On Thu, 30 Apr 2020 10:14:57 +0100
"Burakov, Anatoly" <anatoly.burakov@intel.com> wrote:

> On 30-Apr-20 5:14 AM, 陈亚辉-云杉研发部 wrote:
> > Deleting xdg_runtime_dir and fallback, runtime_dir will always be 
> > "/var/run" defined by code:
> > static const char *default_runtime_dir = "/var/run"
> >   
> 
> I'm not sure this is a good solution. Generally, IMO, having separate 
> directories for DPDK processes for different users is a good thing. 
> Also, XDG directory exists for a reason, and i think on some distros 
> /var/run is not even there any more (or symlinked to /run, or...).
> 
> So, i don't think this is the way to go. David, thoughts?
> 

The unix-domain sockets should be using the abstract socket
naming which would solve a bunch of problems like removing on program
crash, SELinux, and container namepaces.

See unix(7) for more infomation.

  reply	other threads:[~2020-04-30 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  4:14 陈亚辉-云杉研发部
2020-04-30  9:14 ` Burakov, Anatoly
2020-04-30 16:09   ` Stephen Hemminger [this message]
2020-04-30 16:36     ` Bruce Richardson
  -- strict thread matches above, loose matches on Subject: below --
2020-04-15 10:06 陈亚辉-云杉研发部
2020-04-17 13:52 ` Burakov, Anatoly

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=20200430090902.0add5a96@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=goodluckwillcomesoon@gmail.com \
    --cc=jiping@yunshan.net \
    --cc=xiangyang@yunshan.net \
    /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).