On Mon, Jul 17, 2023 at 4:54 PM Sivaprasad Tummala
<sivaprasad.tumm...@amd.com> wrote:
>
> Deprecation notice to add "rte_eventdev_port_data" field to
> ``rte_event_fp_ops`` for callback support.
>
> Signed-off-by: Sivaprasad Tummala <sivaprasad.tumm...@amd.com>

Acked-by: Jerin Jacob <jer...@marvell.com>


> ---
>  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.
>
> --
> 2.34.1
>

Reply via email to