From 57e03d2a620534cee72a54396d799a0a6c1ca2d5 Mon Sep 17 00:00:00 2001 From: Arek Kusztal Date: Wed, 14 Oct 2020 06:07:00 +0100 Subject: [PATCH] doc: remove notice about AES-GCM IV and J0 This patch removes information about deprecation of AES-GCM/GMAC API for IV without J0. Fixes: fac52fb26a54 ("cryptodev: add option to support both IV and J0 for GCM") Cc: stable@dpdk.org Signed-off-by: Arek Kusztal --- doc/guides/rel_notes/deprecation.rst | 6 ------ 1 file changed, 6 deletions(-) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 22aecf0bab..43e0e09be5 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -132,12 +132,6 @@ Deprecation Notices will be limited to maximum 256 queues. Also compile time flag ``RTE_ETHDEV_QUEUE_STAT_CNTRS`` will be removed. -* 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``, - ``rte_crypto_aead_xform`` is set to zero. When IV length is greater or equal - to one it means it represents IV, when is set to zero it means J0 is used - directly, in this case 16 bytes of J0 need to be passed. - * sched: To allow more traffic classes, flexible mapping of pipe queues to traffic classes, and subport level configuration of pipes and queues changes will be made to macros, data structures and API functions defined -- 2.20.1