[dpdk-dev] [PATCH v2] config: disable RTE_NEXT_ABI by default

Bruce Richardson bruce.richardson at intel.com
Fri Oct 5 11:13:52 CEST 2018


On Thu, Oct 04, 2018 at 05:55:34PM +0200, Thomas Monjalon wrote:
> 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).
> 
I'd keep it as is. As said, I'm not sure it's being used right now anyway.


More information about the dev mailing list