On Wed, Jul 12, 2023 at 11:01 PM Sivaprasad Tummala <sivaprasad.tumm...@amd.com> wrote: > > Deprecation notice to add "rte_eventdev_port_data" field to
Could you share the rational for why rte_eventdev_port_data needs to be added? > ``rte_event_fp_ops`` for callback support. > > Signed-off-by: Sivaprasad Tummala <sivaprasad.tumm...@amd.com> > --- > doc/guides/rel_notes/deprecation.rst | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/doc/guides/rel_notes/deprecation.rst > b/doc/guides/rel_notes/deprecation.rst > index 8e1cdd677a..2c69338818 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -133,6 +133,10 @@ 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. This > changes > + the size of rte_event_fp_ops and result in ABI change. > + > * flow_classify: The flow_classify library and example have no maintainer. > The library is experimental and, as such, it could be removed from DPDK. > Its removal has been postponed to let potential users report interest > -- > 2.34.1 >