From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id DD6B3A0487 for ; Thu, 4 Jul 2019 21:52:46 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 820141E20; Thu, 4 Jul 2019 21:52:46 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 24A8C2BE3 for ; Thu, 4 Jul 2019 21:52:44 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9C08E21550; Thu, 4 Jul 2019 15:52:43 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Jul 2019 15:52:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=FvvfUllztWs+fNFRsYOWMuqpvoKn/xp6x5ZVlCrUgIk=; b=M9uAF0H3pIUF sSTm8QFiQaDamelOwyxQ7+t/fMOCzC2GFhHorDjjXEvvRfXqKzDTHRZvTR1o+1SC g0tiF9VTPXc4a4XLy7Fu4/5RLQJ/jqLTdmwMeD9ljNFuXMIvE6Q7P/AIbrEF5igW vybkkQT+vYy2ymT4ZAESbT/f4i5C/0A= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=FvvfUllztWs+fNFRsYOWMuqpvoKn/xp6x5ZVlCrUg Ik=; b=sAkd0rH2SvEoPSEhZg0wKdAYoQ0AJlDrceE28c+z5VB1EM9xho1Al+cpO AvvLTpK6c2f/WJyRWgQO9UBzuvufdEZqP8HeJXSiCgLmp2rABuzKm6jIrKHsF9rm 5E0d5oZoCB/vmYd6Kkz//W9fktyUyLXviVHNyD5PNTHgeBDtgLgOdbEjBIG84xfk AXu60nQFXLP6RySeHPeCW6ba1YL3G1T+3jl8vG0TvkEy6dDAIJwflArKcFc3Uont zoY2lngJxJfxDJ2uhLrN1uHKNC/6WvELBKNOaK+fKl+qiA+ggOIfRTJt9+a5D8Tx 3naV+WdRphE/9P6r2DpgJ0P06UeuQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrfedvgddugeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedu X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id E1AF9380089; Thu, 4 Jul 2019 15:52:42 -0400 (EDT) From: Thomas Monjalon To: David Marchand , Anatoly Burakov Cc: dev@dpdk.org, Stephen Hemminger Date: Thu, 04 Jul 2019 21:52:40 +0200 Message-ID: <2038331.MNQvCC97BZ@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 00/14] Make shared memory config non-public 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 04/07/2019 10:09, David Marchand: > I just want to state two approaches to merge these changes: > - the first one would be to split this series in two > - take the first part of this series now, but mark the new API > "experimental" > - postpone the merge to 19.11 of the second part, which starts at the > hiding rte_mem_config patch > - the second one is taking these changes in one go > > The second one is the quicker and the more straightforward but it leaves > the risk of having missed something and we must break the ABI again in > 19.11. > The risk is quite low, given the changes. > > > Thomas, comments? OK to merge it in one go. Please, can we merge it tomorrow?