From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mem: share legacy and single file segments mode with secondaries Date: Wed, 19 Sep 2018 10:56:44 +0200 Message-ID: <2271639.JqVHzU0O9l@xps> References: <98f283ce5bcf8973c5c08d13f4fbfe375ded6ebf.1535368896.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Anatoly Burakov Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 92CB91B53 for ; Wed, 19 Sep 2018 10:56:46 +0200 (CEST) In-Reply-To: <98f283ce5bcf8973c5c08d13f4fbfe375ded6ebf.1535368896.git.anatoly.burakov@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 27/08/2018 14:24, Anatoly Burakov: > Currently, command-line switches for legacy mem mode or single-file > segments mode are only stored in internal config. This leads to a > situation where these flags have to always match between primary > and secondary, which is bad for usability. > > Fix this by storing these flags in the shared config as well, so > that secondary process can know if the primary was launched in > single-file segments or legacy mem mode. > > This bumps the EAL ABI, however there's an EAL deprecation notice > already in place[1] for a different feature, so that's OK. You need to update the release notes: - ABI change section - library version section Thanks