From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 13464A056A; Wed, 10 Mar 2021 18:27:49 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9BBA722A3AF; Wed, 10 Mar 2021 18:27:48 +0100 (CET) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mails.dpdk.org (Postfix) with ESMTP id BC82E22A348 for ; Wed, 10 Mar 2021 18:27:46 +0100 (CET) IronPort-SDR: 08L0Exrvp0kFiA2Z6MjRozHNK/vreReNsXlJVoBUJCbPipJ4hFxvBp6w+Lvf3PmXm7FauMl8cG 4yTOPw9MvKng== X-IronPort-AV: E=McAfee;i="6000,8403,9919"; a="208328594" X-IronPort-AV: E=Sophos;i="5.81,237,1610438400"; d="scan'208";a="208328594" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Mar 2021 09:27:27 -0800 IronPort-SDR: m0KN0gyg/CRJzBVu4jQWGDYMQmrulwQdTBlDbaocNZi6gKVn/ALPTur9EVho5UJMl5VJ+XUUKZ jc0fQrd1wgkw== X-IronPort-AV: E=Sophos;i="5.81,237,1610438400"; d="scan'208";a="509744910" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.9.86]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 10 Mar 2021 09:27:26 -0800 Date: Wed, 10 Mar 2021 17:27:17 +0000 From: Bruce Richardson To: Stephen Hemminger Cc: dev@dpdk.org, Stephen Hemminger Message-ID: <20210310172717.GE1267@bricha3-MOBL.ger.corp.intel.com> References: <20210310172137.59938-1-sthemmin@microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210310172137.59938-1-sthemmin@microsoft.com> Subject: Re: [dpdk-dev] [PATCH] eal: allow user to override DPDK runtime path X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Mar 10, 2021 at 09:21:37AM -0800, Stephen Hemminger wrote: > There can be cases such as containers or other runtime environments > where DPDK may not be able to access the default runtime path. > This patch introduces DPDK_RUNTIME_DIR as an environment variable > to allow controlling and overriding the path. > > The example we have is DPDK application running in an untrusted > systemd container. In this case, it is not root, and XDG_RUNTIME_DIR > is not set (since it is not a user application), and /tmp is > blocked. The correct place for this application is to use /run. > > In any case, hard coded path assumptions are a problem. > > Signed-off-by: Stephen Hemminger > --- Basic question, if the user/operator can set DPDK_RUNTIME_DIR in the container, can they not also set XDG_RUNTIME_DIR?