From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 96A3C5F5D for ; Thu, 8 Mar 2018 17:04:17 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E0A3620FA9; Thu, 8 Mar 2018 11:04:16 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 08 Mar 2018 11:04:16 -0500 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=yImoSeBsnZh4cojFmDJaxy5F3v +s+QErF6ia3D3tw1o=; b=q61BYd++hR3Ul1frp7kAbFGRzKJREugN6FhZf3XZ9x u4CvPjhfl5uDLeXqpOjBZC5XZfJl9pD602NIQ9mGN2vdeKJqv8wfTZOB8o77y7pA veR8smq1P7YOLLUbpKPIW4YaUa0FhGwneG8rku5N2vO2+Mf0+66xbtqL3xGDQtF+ 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=fm2; bh=yImoSe BsnZh4cojFmDJaxy5F3v+s+QErF6ia3D3tw1o=; b=E6JaAUqKz6JS19eMF+daV7 fMleN5yr9BgP5H7ZTZN98WppYE1GU7S0vfIFKbkOALlPdc0HmiKx/ipUCrCI89pp eszvE2Gc3ofjy7Gp/ktbdgZAn10S/RJJS8UgkygF/bdX3KD43XlNIPLbZBae/v/0 9beGxtHLEhqA2u6/e+JCC5kV7MflgIIQY2J/K+3+bCQZDfPKdJZY/WQovcx1SESX WG7HqlfZz79Ga16s78M50foF8aawc7mooQy4ywXyZ6T3bHFVHTD/52cxRKLtLrE8 WPp9EiNKXtCSCWGuESPDbPPBCAhJERR1lmqu7OvoGxnA4NfBUAKRWfDxWC0hutng == 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 DEC957E171; Thu, 8 Mar 2018 11:04:15 -0500 (EST) From: Thomas Monjalon To: Neil Horman Cc: Ferruh Yigit , John McNamara , Marko Kovacevic , dev@dpdk.org, Luca Boccassi , Christian Ehrhardt Date: Thu, 08 Mar 2018 17:04:01 +0100 Message-ID: <4097404.y7j9CXhnSi@xps> In-Reply-To: <20180308153504.GA32578@hmswarspite.think-freely.org> References: <20180307174422.118291-1-ferruh.yigit@intel.com> <1672091.0Tzq5VA8o7@xps> <20180308153504.GA32578@hmswarspite.think-freely.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [RFC] config: remove RTE_NEXT_ABI 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: Thu, 08 Mar 2018 16:04:17 -0000 08/03/2018 16:35, Neil Horman: > On Thu, Mar 08, 2018 at 04:17:00PM +0100, Thomas Monjalon wrote: > > 08/03/2018 12:43, Ferruh Yigit: > > > On 3/8/2018 8:05 AM, Thomas Monjalon wrote: > > > > 07/03/2018 18:44, Ferruh Yigit: > > > >> After experimental API process defined do we still need RTE_NEXT_ABI > > > >> config and process which has similar targets? > > > > > > > > They are different targets. > > > > Experimental API is always enabled but may be avoided by applications. > > > > Next ABI can be used to break ABI without notice and disabled to keep > > > > old ABI compatibility. It is almost never used because it is preferred > > > > to keep ABI compatibility with rte_compat macros, or wait a deprecation > > > > period after notice. > > > > > > OK, I see. > > > > > > Shouldn't we disable it by default at least? Otherwise who is not paying > > > attention to this config option will get and ABI/API break. > > > > Yes I think you are right, it can be disabled by default. > > > I would agree, there seems to be overlap here, and the experimental tagging can > cover what the NEXT_API flag is meant to do. It can be removed I think. It is not NEXT_API but NEXT_ABI. Why do you think it overlaps experimental API tagging?