From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 20BB521F11; Wed, 19 Sep 2018 04:56:46 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 19 Sep 2018 04:56:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=jaTLN9tNfwud7ZRJH9yQPmmE64 DF4wi9M+UtjdDWYg0=; b=Nd2soetXCJkVhWrRTgc74FKPCrfqn6d0WcidmfsZ+f U4wATvpl7pLRQlBtajumO4ygaG0m5rL/tNlOm1OKjSFigVWGUjCCaWM9qqQkRKYw eHTjGV1ufsHXjjeY/U1exUUtJ26TmKO5n4NElc9+eGRG1AocSyaiFXmSt/My7r3y s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=jaTLN9 tNfwud7ZRJH9yQPmmE64DF4wi9M+UtjdDWYg0=; b=f5dhWQvBUS7stK6kIZJtzC FWd+UeZLvcBX+qd6v8YiMkJrHRS/Fpqv8yLRszmwqqWk5MfbgG5BT/i92MLu1ML3 WGDLbd3lzYiT/pve2v+ON/ODQ+O0cWCeGYUuq8x10wH8PYJSqu43fWrHZyOEGtUY waao5TKPyemsxE+9+WppULjJrvwwMDgAQB7BCcaTMKbVJKPvduN/RlWhv0H+Erwa QLvpq2X9An+3MWq9+yQ6DoQFgop9SUemehYxpKdqFE8YX2EBYuhpIrQ93yAsOnlO 6kUaNWjtvjY9dwXuIVEbQzeP1+wEDWo1Qm3Qqqu8N0yNMgFQEwtTxYTJju69pT5A == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 281EB102D3; Wed, 19 Sep 2018 04:56:45 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org Date: Wed, 19 Sep 2018 10:56:44 +0200 Message-ID: <2271639.JqVHzU0O9l@xps> In-Reply-To: <98f283ce5bcf8973c5c08d13f4fbfe375ded6ebf.1535368896.git.anatoly.burakov@intel.com> References: <98f283ce5bcf8973c5c08d13f4fbfe375ded6ebf.1535368896.git.anatoly.burakov@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] mem: share legacy and single file segments mode with secondaries X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Sep 2018 08:56:46 -0000 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