From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 8064F5F14
 for <dev@dpdk.org>; Thu,  8 Mar 2018 16:17:19 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id D17D22118B;
 Thu,  8 Mar 2018 10:17:15 -0500 (EST)
Received: from frontend2 ([10.202.2.161])
 by compute1.internal (MEProxy); Thu, 08 Mar 2018 10:17:15 -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=KJDmPsaGIkeQ8GmkE//HkJQiaz
 8BE8Qj3TMuLB+1/FI=; b=PuD1wHWjhj+pTmaiuSt9pf0aiUbaXXILSxemietRL3
 GZ5I2RAT5pEJjLamRblrJ/jkQuHL0EMOc7BH0qOn7ob6VqvBSCyv9dq1ViSjsdJ4
 DH8hSImD+1zLNXGzpqmOry5Fz1TddBBN62iOr8jtZ0RWHXnmHCya1KfpMdSJ0QFi
 g=
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=KJDmPs
 aGIkeQ8GmkE//HkJQiaz8BE8Qj3TMuLB+1/FI=; b=E3Qcmy/uPnoJEwKQ+xwG6X
 EBjP+A1w4bqQqjazoV8oCIBFrXCMq3IwtNWDYcB9JEtksKuYzMpzjv/W4O+SUCKn
 Y42n49qUtXrIG5uF+1PTnMUvGsxDRFLpxLpxnZy20LZaLkPZ/4VSaIPnWEf4PJ84
 l+WsWAmDXsVmKQ/PYWhyR3p+3h9Xc5DxC2FLoIwNiu0qsDgLlUXMTXjIaNUD/vaE
 mh7IJ9lMYsty2owOCczB+Y9JnVEgtmfREpBuBkbSRenkWimQJxOGdTrV1OtlSebq
 NT5xwt+TV3HtLduPo2+q3rjrauPYsyuZfVd/IOzBrYbBuhVV5w4b7XWCJmD3J5Vw
 ==
X-ME-Sender: <xms:-1OhWsl3QBJesy00SauAdiFJm6szORFtnkPOsUFM_ZlOeBWlE2DAKg>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id D154E24814;
 Thu,  8 Mar 2018 10:17:14 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
 John McNamara <john.mcnamara@intel.com>,
 Marko Kovacevic <marko.kovacevic@intel.com>, dev@dpdk.org,
 Luca Boccassi <bluca@debian.org>,
 Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Thu, 08 Mar 2018 16:17:00 +0100
Message-ID: <1672091.0Tzq5VA8o7@xps>
In-Reply-To: <cc7522b2-d0b1-6522-527e-3e247c59ba62@intel.com>
References: <20180307174422.118291-1-ferruh.yigit@intel.com>
 <6880912.l9NoFy8GUE@xps> <cc7522b2-d0b1-6522-527e-3e247c59ba62@intel.com>
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 <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: Thu, 08 Mar 2018 15:17:19 -0000

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.