[PATCH v2] doc: announce single-event enqueue/dequeue ABI change

[David Marchand]

On Mon, Oct 14, 2024 at 9:19 AM Jerin Jacob <jerinjacobk at gmail.com> wrote:
> On Sun, Oct 13, 2024 at 12:27 PM Mattias Rönnblom <hofors at lysator.liu.se> wrote:
> >
> > On 2024-10-11 16:42, David Marchand wrote:
> > > On Wed, Jul 5, 2023 at 1:18 PM Mattias Rönnblom
> > > <mattias.ronnblom at ericsson.com> wrote:
> > >>
> > >> Announce the removal of the single-event enqueue and dequeue
> > >> operations from the eventdev ABI.
> > >>
> > >> Signed-off-by: Mattias Rönnblom <mattias.ronnblom at ericsson.com>
> > >>
> > >> ---
> > >> PATCH v2: Fix commit subject prefix.
> > >> ---
> > >>   doc/guides/rel_notes/deprecation.rst | 8 ++++++++
> > >>   1 file changed, 8 insertions(+)
> > >>
> > >> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> > >> index 66431789b0..ca192d838d 100644
> > >> --- a/doc/guides/rel_notes/deprecation.rst
> > >> +++ b/doc/guides/rel_notes/deprecation.rst
> > >> @@ -153,3 +153,11 @@ Deprecation Notices
> > >>     The new port library API (functions rte_swx_port_*)
> > >>     will gradually transition from experimental to stable status
> > >>     starting with DPDK 23.07 release.
> > >> +
> > >> +* eventdev: The single-event (non-burst) enqueue and dequeue
> > >> +  operations, used by static inline burst enqueue and dequeue
> > >> +  functions in <rte_eventdev.h>, will be removed in DPDK 23.11. This
> > >> +  simplification includes changing the layout and potentially also the
> > >> +  size of the public rte_event_fp_ops struct, breaking the ABI. Since
> > >> +  these functions are not called directly by the application, the API
> > >> +  remains unaffected.
> > >
> > > Looks like it was missed in 23.11, can/should we finish this cleanup in 24.11?
> > >
> > >
> >
> > Yes, sure. Jerin, should I submit a patch?
>
> David/Thomas, We should be OK to take as rc2. Right? If so, OK.

Afaiu, this cleanup involves removing driver facing API only, and some
driver cleanups.
It should have no impact on application API.

If so, it fits in rc2.


-- 
David Marchand