From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id B36EA1B556 for ; Thu, 4 Oct 2018 17:55:39 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 75E3E2F2; Thu, 4 Oct 2018 11:55:37 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Oct 2018 11:55:37 -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=KA3BmN76xRlyAMqjTYcEveyHc/9BAQN2kba5BXp6h3s=; b=iBPJfid6g5ar E8xNNTbSOpuo2B0Tg74En5DLhkM7JZVr4Hud/pdqShKQ3XSs/mM/Yt0nh/jBOrIt unzmlrTnPJ9GgQnojLPSY8DmXNkEEBaTzOsNfFh5M6GGxf5mk3V6QJ/5IyaF8COR 2dNAhj/QzKppQXeykwymLFvF0gJKRW4= 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=KA3BmN76xRlyAMqjTYcEveyHc/9BAQN2kba5BXp6h 3s=; b=m7mLW2+xHQ3oyFxZmGkFJYqVULkcP15pLlthK+VK9RV7fkPu695bNketF Qu1Y10P9534ob+65KhhuZ4c/bUO3yt04b1BBELP+Y87/AB7iHFy6BPqx23AfmVVA gOt2y4SxH3oKmxKedYHEja9kAj74FQ2zV/QWYhLBjSa2bmyZkhrwUfSEZ2WQiKQp oHcyJDBMMXTFN7EiHs29OJT9CZRDg5Gk2l+tB4HZq0q0Uh68JzEe/sAqXkyrEyAI 6r+jd6rul8aNkFXyAkm/ojUl7NY0wVSX8O4ylSaRwz7XyddGqmx626s3Lvb8xs/K owyo/YwHsXzCx1bzkhMeKe9afRH7w== X-ME-Sender: 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 A89D5102D7; Thu, 4 Oct 2018 11:55:35 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, Neil Horman , Luca Boccassi , Christian Ehrhardt Date: Thu, 04 Oct 2018 17:55:34 +0200 Message-ID: <33456122.koQSlajCb5@xps> In-Reply-To: <56a42359-9ead-7c33-72a3-1d89d56f383c@intel.com> References: <20181004154306.65867-1-ferruh.yigit@intel.com> <1785611.eL8Z1dKoq2@xps> <56a42359-9ead-7c33-72a3-1d89d56f383c@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] config: disable RTE_NEXT_ABI by default 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, 04 Oct 2018 15:55:40 -0000 04/10/2018 17:28, Ferruh Yigit: > On 10/4/2018 4:10 PM, Thomas Monjalon wrote: > > 04/10/2018 17:48, Ferruh Yigit: > >> Enabling RTE_NEXT_ABI means to enable APIs that break the ABI for > >> the current release and these APIs are targeted for further release. > > > > It seems nobody is using it in last releases. > > > >> RTE_NEXT_ABI shouldn't be enabled by default. > > > > The reason for having it enabled by default is that when you build DPDK > > yourself, you probably want the latest features. > > If packaged properly for stability, it is easy to disable it in > > the package recipe. > > My concern was (if this has been used), user may get unstable APIs and without > explicitly being aware of it. I am OK with both defaults (enabled or disabled).