[dpdk-dev] [PATCH v5] build: disable experimental API check internally

[David Marchand]

On Fri, Apr 17, 2020 at 3:44 PM Trahe, Fiona <fiona.trahe at intel.com> wrote:
>
> Hi David,
>
> > -----Original Message-----
> > From: David Marchand <david.marchand at redhat.com>
> > Sent: Friday, April 17, 2020 2:23 PM
> > To: Trahe, Fiona <fiona.trahe at intel.com>
> > Cc: dev <dev at dpdk.org>; Jerin Jacob <jerinjacobk at gmail.com>; Pavan Nikhilesh
> > <pbhagavatula at marvell.com>; Richardson, Bruce <bruce.richardson at intel.com>; Thomas Monjalon
> > <thomas at monjalon.net>; Yigit, Ferruh <ferruh.yigit at intel.com>; Hemant Agrawal
> > <hemant.agrawal at nxp.com>
> > Subject: Re: [dpdk-dev] [PATCH v5] build: disable experimental API check internally
> >
> > On Fri, Apr 17, 2020 at 12:21 PM Trahe, Fiona <fiona.trahe at intel.com> wrote:
> > > I see this is already applied.
> > >
> > > However,
> > > rte_cryptodev_queue_pair_setup() calls
> > > rte_cryptodev_sym_get_existing_header_session_size()
> > > The former is a stable API, the latter is experimental.
> > > So I expect the build to break when ALLOW_EXPERIMENTAL_API is disabled.
> [Fiona] Thanks for confirming where the flag is.
> But I think you've missed my point.
> What about this problem?

- dpdk-test-crypto-perf is built as part of the dpdk compilation itself.
There is no user to be made aware of its use of experimental API.

Now if you are talking about how the crypto API is bent in that it
exposes a stable ABI with an underlying experimental ABI, this has
nothing to do with the flag change.

- But if you want to check crypto experimental api, then try to
disable the flag in examples making use of them.


-- 
David Marchand