All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, bruce.richardson@intel.com
Subject: [PATCH v3 0/4] Clean up EAL runtime data paths
Date: Mon, 14 May 2018 17:27:38 +0100	[thread overview]
Message-ID: <cover.1526315209.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <cover.1525090086.git.anatoly.burakov@intel.com>

As has been suggested [1], all DPDK runtime paths should be put
into a single place. This patchset accomplishes exactly that.

If running as root, all files will be put under /var/run/dpdk/<prefix>,
otherwise they will be put under $XDG_RUNTIME_PATH/dpdk/<prefix>, or, if
that environment variable is not defined, all files will go under
/tmp/dpdk/<prefix>.

[1] http://dpdk.org/dev/patchwork/patch/38688/

v3:
- Rebase on rc2
- Leave rte_config path in place, to be fixed for next release

v2:
- Rebase on rc1

Anatoly Burakov (4):
  eal: remove unused define
  eal: rename function returning hugepage data path
  eal: add directory for DPDK runtime data
  eal: move all runtime data into DPDK runtime dir

 lib/librte_eal/bsdapp/eal/eal.c          | 70 +++++++++++++++++++++++++++++++
 lib/librte_eal/common/eal_filesystem.h   | 71 +++++++++++---------------------
 lib/librte_eal/linuxapp/eal/eal.c        | 69 +++++++++++++++++++++++++++++++
 lib/librte_eal/linuxapp/eal/eal_memory.c | 10 +++--
 4 files changed, 169 insertions(+), 51 deletions(-)

-- 
2.7.4

  parent reply	other threads:[~2018-05-14 16:27 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-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
2018-04-30 12:08   ` [PATCH v2 4/4] eal: move all runtime data into DPDK runtime dir Anatoly Burakov
2018-05-09 15:59   ` [PATCH v2 0/4] Clean up EAL runtime data paths 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   ` Anatoly Burakov [this message]
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-05-14 22:45     ` [PATCH v3 0/4] Clean up EAL runtime data paths 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=cover.1526315209.git.anatoly.burakov@intel.com \
    --to=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.