From: Bruce Richardson <bruce.richardson@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] fbarray: make all fbarrays hidden files
Date: Mon, 23 Apr 2018 13:48:32 +0100 [thread overview]
Message-ID: <20180423124832.GA100540@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <738d08e521a8987ceeb2748db5b765d8b8531e54.1524481846.git.anatoly.burakov@intel.com>
On Mon, Apr 23, 2018 at 12:14:13PM +0100, Anatoly Burakov wrote:
> fbarray stores its data in a shared file, which is not hidden.
> This leads to polluting user's HOME directory with visible
> files when running DPDK as non-root. Change fbarray to always
> create hidden files by default.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
>
> Notes:
> Is /tmp always user-accessible? Maybe not use home
> directory at all?
>
Good change.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
A further improvement would to put the files as not-hidden but inside a
hidden subdirectory e.g. ".dpdk"
next prev parent reply other threads:[~2018-04-23 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 11:14 Anatoly Burakov
2018-04-23 12:48 ` Bruce Richardson [this message]
2018-04-23 13:47 ` Burakov, Anatoly
2018-04-23 19:56 ` Thomas Monjalon
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=20180423124832.GA100540@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
/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).