d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

ethdev: remove deprecation notice for packet type set

Browse Source 
The functionality is added, but the deprecation notice is not
removed.

Fixes: 5d4813acda2c ("ethdev: add packet type range function")

Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
This commit is contained in:
Andrew Rybchenko 2019-11-19 12:12:14 +00:00 committed by Ferruh Yigit
parent 8f64f2846d
commit 6355f12370
1 changed files with 0 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/guides/rel_notes/deprecation.rst
View File

@ -68,21 +68,6 @@ Deprecation Notices
In 19.11 PMDs will still update the fields even when the offloads are not In 19.11 PMDs will still update the fields even when the offloads are not
enabled. enabled.
* ethdev: New function ``rte_eth_dev_set_supported_ptypes`` will be added in
19.11.
This will allow application to request PMD to set specific ptypes defined
through ``rte_eth_dev_set_supported_ptypes`` in ``rte_mbuf::packet_type``.
If application doesn't want any ptype information it can call
``rte_eth_dev_set_supported_ptypes(ethdev_id, RTE_PTYPE_UNKNOWN)`` and PMD
will set ``rte_mbuf::packet_type`` to ``0``.
If application doesn't call ``rte_eth_dev_set_supported_ptypes`` PMD can
return ``rte_mbuf::packet_type`` with ``rte_eth_dev_get_supported_ptypes``.
If application is interested only in L2/L3 layer, it can inform the PMD
to update ``rte_mbuf::packet_type`` with L2/L3 ptype by calling
``rte_eth_dev_set_supported_ptypes(ethdev_id, RTE_PTYPE_L2_MASK | RTE_PTYPE_L3_MASK)``.
This scheme will allow PMDs to avoid lookup to internal ptype table on Rx and
thereby improve Rx performance if application wishes do so.
* cryptodev: support for using IV with all sizes is added, J0 still can * cryptodev: support for using IV with all sizes is added, J0 still can
be used but only when IV length in following structs ``rte_crypto_auth_xform``, be used but only when IV length in following structs ``rte_crypto_auth_xform``,
``rte_crypto_aead_xform`` is set to zero. When IV length is greater or equal ``rte_crypto_aead_xform`` is set to zero. When IV length is greater or equal