From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 649171B518 for ; Thu, 4 Oct 2018 17:28:33 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Oct 2018 08:28:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,340,1534834800"; d="scan'208";a="262854637" Received: from fyigit-mobl.ger.corp.intel.com (HELO [10.237.221.49]) ([10.237.221.49]) by orsmga005.jf.intel.com with ESMTP; 04 Oct 2018 08:28:27 -0700 To: Thomas Monjalon Cc: dev@dpdk.org, Neil Horman , Luca Boccassi , Christian Ehrhardt References: <20181004154306.65867-1-ferruh.yigit@intel.com> <20181004154829.66523-1-ferruh.yigit@intel.com> <1785611.eL8Z1dKoq2@xps> From: Ferruh Yigit Openpgp: preference=signencrypt Message-ID: <56a42359-9ead-7c33-72a3-1d89d56f383c@intel.com> Date: Thu, 4 Oct 2018 16:28:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1785611.eL8Z1dKoq2@xps> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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:28:33 -0000 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.