[dpdk-dev] [PATCH v4] doc: announce ring API change
stephen at networkplumber.org
Fri May 10 16:58:55 CEST 2019
On Fri, 10 May 2019 14:53:56 +0000
"Eads, Gage" <gage.eads at intel.com> wrote:
> > 01/02/2019 15:36, Gage Eads:
> > > In order to support the non-blocking ring, an API change
> > > (additional argument to rte_ring_get_memsize()) is required in
> > > librte_ring. This commit updates the deprecation notice to pave the
> > > way for its inclusion in 19.08.
> > >
> > >  http://mails.dpdk.org/archives/dev/2019-January/124162.html
> > >
> > > Signed-off-by: Gage Eads <gage.eads at intel.com>
> > There is still no agreement on this change?
> Still none. I was hoping this discussion (http://mails.dpdk.org/archives/dev/2019-April/129229.html) would lead to some clear direction, but at this point the effort is stalled.
The fundamental tradeoff is between non-blocking rings and ABI breakage.
Why not have a new ring type for non-blocking rings since non-blocking
rings are not necessary for all use cases.
More information about the dev