From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <anatoly.burakov@intel.com> Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 541C91C62A for <dev@dpdk.org>; Mon, 14 May 2018 10:26:31 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 May 2018 01:26:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,399,1520924400"; d="scan'208";a="54947434" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.252.6.248]) ([10.252.6.248]) by fmsmga001.fm.intel.com with ESMTP; 14 May 2018 01:26:28 -0700 To: Thomas Monjalon <thomas@monjalon.net>, Bruce Richardson <bruce.richardson@intel.com>, "Van Haaren, Harry" <harry.van.haaren@intel.com> Cc: "dev@dpdk.org" <dev@dpdk.org> References: <cover.1524657197.git.anatoly.burakov@intel.com> <E923DB57A917B54B9182A2E928D00FA65E135FE5@IRSMSX102.ger.corp.intel.com> <20180509161142.GA14700@bricha3-MOBL.ger.corp.intel.com> <1920136.Nh2Sl1zDJV@xps> From: "Burakov, Anatoly" <anatoly.burakov@intel.com> Message-ID: <e24a3d4f-fce6-9cf2-c027-b1916cc89340@intel.com> Date: Mon, 14 May 2018 09:26:28 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1920136.Nh2Sl1zDJV@xps> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2 0/4] Clean up EAL runtime data paths X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Mon, 14 May 2018 08:26:31 -0000 On 09-May-18 8:03 PM, Thomas Monjalon wrote: > 09/05/2018 18:11, Bruce Richardson: >> On Wed, May 09, 2018 at 04:59:39PM +0100, Van Haaren, Harry wrote: >>>> 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 0/4] Clean up EAL runtime data paths >>>> >>>> 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/ >>>> >>>> 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 >>> >>> <snip> >>> >>> >>> No full code review, high level comments: >>> >>> We have to be careful in changing /var/run/.rte_config, which has always been >>> the default DPDK primary application lockfile. This has been used to identify >>> if a primary DPDK application is alive (see rte_eal_primary_proc_alive()) and >>> possibly the write-lock on this file is checked by other tools/utilities directly >>> without any DPDK function call. >>> >>> Changing the filepath just before a release isn't a good idea - we should treat >>> this as an ABI/API break, as the change will break functionality in other projects >>> such as CollectD[1], which (by default ;) rely on the defaults. There is a config >>> file for CollectD to manually override the location, but this will cause headaches >>> from a usability POV. >>> >>> I'm not opposed to the change - particularly as I gather the new memory subsystem >>> causes a number of lockfiles to be created - but we must do our due diligence and >>> give other projects fair-warning that this change is coming. >>> >>> As such, I recommend this patchset in its current form (particularly patches 2,3,4) >>> to be deferred past 18.05. >>> >>> >> What about if we keep the .rte_config file in the same place but move the >> rest? The number of new files causes quite a bit of clutter. We can then >> have a deprecation notice for the move in 18.05 and finish the cleanup in >> 18.08. > > I agree > Thanks for catching this, Harry. I'll resubmit the patches then, along with a deprecation notice about /var/run/.<prefix>_config. -- Thanks, Anatoly