doc: remove deprecation notices for eventdev
All deprecation notice targeted for v21.11 of eventdev has been committed in the following commits, remove deprecation notices. Fixes:3c838062b9
("eventdev: introduce event vector Rx capability") Fixes:929ebdd543
("eventdev/eth_rx: simplify event vector config") Fixes:295c053f90
("eventdev: hide event device related structures") Fixes:dd451ad152
("doc: remove event crypto metadata deprecation note") Reported-by: David Marchand <david.marchand@redhat.com> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
This commit is contained in:
parent
578402f2d5
commit
07ed904bf1
@ -110,32 +110,6 @@ Deprecation Notices
|
||||
pointer for the private data to the application which can be attached
|
||||
to the packet while enqueuing.
|
||||
|
||||
* eventdev: The file ``rte_eventdev_pmd.h`` will be renamed to ``eventdev_driver.h``
|
||||
to make the driver interface as internal and the structures ``rte_eventdev_data``,
|
||||
``rte_eventdev`` and ``rte_eventdevs`` will be moved to a new file named
|
||||
``rte_eventdev_core.h`` in DPDK 21.11.
|
||||
The ``rte_`` prefix for internal structures and functions will be removed across the
|
||||
library.
|
||||
The experimental eventdev trace APIs and ``rte_event_vector_pool_create``,
|
||||
``rte_event_eth_rx_adapter_vector_limits_get`` will be promoted to stable.
|
||||
An 8-byte reserved field will be added to the structure ``rte_event_timer`` to
|
||||
support future extensions.
|
||||
|
||||
* eventdev: The structure ``rte_event_eth_rx_adapter_queue_conf`` will be
|
||||
extended to include ``rte_event_eth_rx_adapter_event_vector_config`` elements
|
||||
and the function ``rte_event_eth_rx_adapter_queue_event_vector_config`` will
|
||||
be removed in DPDK 21.11.
|
||||
|
||||
An application can enable event vectorization by passing the desired vector
|
||||
values to the function ``rte_event_eth_rx_adapter_queue_add`` using
|
||||
the structure ``rte_event_eth_rx_adapter_queue_add``.
|
||||
|
||||
* eventdev: Reserved bytes of ``rte_event_crypto_request`` is a space holder
|
||||
for ``response_info``. Both should be decoupled for better clarity in
|
||||
DPDK 21.11.
|
||||
New space for ``response_info`` can be made by changing
|
||||
``rte_event_crypto_metadata`` type to structure from union.
|
||||
|
||||
* metrics: The function ``rte_metrics_init`` will have a non-void return
|
||||
in order to notify errors instead of calling ``rte_exit``.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user