> > -----Original Message----- > > From: Ferruh Yigit <[email protected]> > > Sent: Tuesday, July 25, 2023 2:11 PM > > To: Sivaprasad Tummala <[email protected]>; [email protected] > > Cc: [email protected]; [email protected]; > > [email protected]; [email protected]; [email protected] > > Subject: Re: [PATCH v1] doc: deprecation notice to add callback data to > > rte_event_fp_ops > > > > On 7/17/2023 12:24 PM, Sivaprasad Tummala wrote: > > > Deprecation notice to add "rte_eventdev_port_data" field to > > > ``rte_event_fp_ops`` for callback support. > > > > > > Signed-off-by: Sivaprasad Tummala <[email protected]> > > > --- > > > doc/guides/rel_notes/deprecation.rst | 7 +++++++ > > > 1 file changed, 7 insertions(+) > > > > > > diff --git a/doc/guides/rel_notes/deprecation.rst > > > b/doc/guides/rel_notes/deprecation.rst > > > index fb771a0305..057f97ce5a 100644 > > > --- a/doc/guides/rel_notes/deprecation.rst > > > +++ b/doc/guides/rel_notes/deprecation.rst > > > @@ -130,6 +130,13 @@ Deprecation Notices > > > ``rte_cryptodev_get_auth_algo_string``, > > ``rte_cryptodev_get_aead_algo_string`` and > > > ``rte_cryptodev_asym_get_xform_string`` respectively. > > > > > > +* eventdev: The struct rte_event_fp_ops will be updated with a new > > > +element > > > + rte_eventdev_port_data to support optional callbacks in DPDK 23.11. > > > + rte_eventdev_port_data is used to hold callbacks registered > > > +optionally > > > + per event device port and associated callback data. By adding > > > +rte_eventdev_port_data > > > + to rte_event_fp_ops, allows to fetch this data for fastpath > > > +eventdev inline functions > > > + in advance. This changes the size of rte_event_fp_ops and result in ABI > > change. > > > + > > > * security: Hide structures ``rte_security_ops`` and ``rte_security_ctx`` > > > as these are internal to DPDK library and drivers. > > > > > > > +techboard, > > > > Request for review/ack, patch is to extend eventdev to support callbacks > per > > packet. > Acked-by: Hemant Agrawal <[email protected]>
Acked-by: Pavan Nikhilesh <[email protected]>
