From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anatoly Burakov Subject: [PATCH v2 0/4] Clean up EAL runtime data paths Date: Mon, 30 Apr 2018 13:08:51 +0100 Message-ID: References: Cc: bruce.richardson@intel.com, thomas@monjalon.net To: dev@dpdk.org Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 91D5EDED for ; Mon, 30 Apr 2018 14:08:58 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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/, otherwise they will be put under $XDG_RUNTIME_PATH/dpdk/, or, if that environment variable is not defined, all files will go under /tmp/dpdk/. [1] http://dpdk.org/dev/patchwork/patch/38688/ 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 | 81 ++++++++++---------------------- lib/librte_eal/linuxapp/eal/eal.c | 69 +++++++++++++++++++++++++++ lib/librte_eal/linuxapp/eal/eal_memory.c | 10 ++-- 4 files changed, 171 insertions(+), 59 deletions(-) -- 2.7.4