All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [PATCH v2 3/4] eal: add directory for DPDK runtime data
Date: Thu, 10 May 2018 14:05:41 +0000	[thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A2EF63F@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <714f609daed88d377d04e41f14ab53bbd72945cd.1525090086.git.anatoly.burakov@intel.com>

Hi,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anatoly Burakov
> Sent: Monday, April 30, 2018 1:09 PM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; thomas@monjalon.net
> Subject: [dpdk-dev] [PATCH v2 3/4] eal: add directory for DPDK runtime data
> 
> Currently, during runtime, DPDK will store a bunch of files here and there (in
> /var/run, /tmp or in $HOME). Fix it by creating a DPDK-specific runtime
> directory, under which all runtime data will be placed. The template for
> creating this runtime directory is the following:
> 
>   <base path>/dpdk/<DPDK prefix>/
> 
> Where <base path> is set to either "/var/run" if run as root, or
> $XDG_RUNTIME_DIR if run as non-root, with a fallback to /tmp if
> $XDG_RUNTIME_DIR is not defined. So, for example, if run as root, by default
> all runtime data will be stored at /var/run/dpdk/rte/.
> 
> There is no equivalent of "mkdir -p", so we will be creating the path step by
> step.
> 
> Nothing uses this new path yet, changes for that will come in next commit.
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
>  lib/librte_eal/bsdapp/eal/eal.c        | 68
> ++++++++++++++++++++++++++++++++++
>  lib/librte_eal/common/eal_filesystem.h |  8 ++++
>  lib/librte_eal/linuxapp/eal/eal.c      | 67
> +++++++++++++++++++++++++++++++++
>  3 files changed, 143 insertions(+)
> 

Looks good to me.
Reviewed-by: Reshma Pattan <reshma.pattan@intel.cm>

  reply	other threads:[~2018-05-10 14:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 12:24 [PATCH 18.05-RC2 0/4] Clean up EAL runtime data paths Anatoly Burakov
2018-04-25 12:24 ` [PATCH 18.05-RC2 1/4] eal: remove unused define Anatoly Burakov
2018-04-26  7:11   ` David Marchand
2018-04-25 12:24 ` [PATCH 18.05-RC2 2/4] eal: rename function returning hugepage data path Anatoly Burakov
2018-04-25 12:24 ` [PATCH 18.05-RC2 3/4] eal: add directory for DPDK runtime data Anatoly Burakov
2018-04-25 12:24 ` [PATCH 18.05-RC2 4/4] eal: move all runtime data into DPDK runtime dir Anatoly Burakov
2018-04-30 12:08 ` [PATCH v2 0/4] Clean up EAL runtime data paths Anatoly Burakov
2018-05-09 15:59   ` Van Haaren, Harry
2018-05-09 16:11     ` Bruce Richardson
2018-05-09 19:03       ` Thomas Monjalon
2018-05-14  8:26         ` Burakov, Anatoly
2018-05-14 16:27   ` [PATCH v3 " Anatoly Burakov
2018-05-14 22:45     ` Thomas Monjalon
2018-05-14 16:27   ` [PATCH v3 1/4] eal: remove unused define Anatoly Burakov
2018-05-14 16:27   ` [PATCH v3 2/4] eal: rename function returning hugepage data path Anatoly Burakov
2018-05-14 16:27   ` [PATCH v3 3/4] eal: add directory for DPDK runtime data Anatoly Burakov
2018-05-14 16:27   ` [PATCH v3 4/4] eal: move all runtime data into DPDK runtime dir Anatoly Burakov
2018-04-30 12:08 ` [PATCH v2 1/4] eal: remove unused define Anatoly Burakov
2018-04-30 12:08 ` [PATCH v2 2/4] eal: rename function returning hugepage data path Anatoly Burakov
2018-05-10 13:14   ` Pattan, Reshma
2018-04-30 12:08 ` [PATCH v2 3/4] eal: add directory for DPDK runtime data Anatoly Burakov
2018-05-10 14:05   ` Pattan, Reshma [this message]
2018-04-30 12:08 ` [PATCH v2 4/4] eal: move all runtime data into DPDK runtime dir Anatoly Burakov

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=3AEA2BF9852C6F48A459DA490692831F2A2EF63F@irsmsx110.ger.corp.intel.com \
    --to=reshma.pattan@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.