* [dpdk-dev] [PATCH v2] doc: remove aes-gcm addition of j0 deprecation notice
@ 2020-10-14 5:07 Arek Kusztal
2020-10-28 11:14 ` Akhil Goyal
0 siblings, 1 reply; 2+ messages in thread
From: Arek Kusztal @ 2020-10-14 5:07 UTC (permalink / raw)
To: dev; +Cc: akhil.goyal, fiona.trahe, Arek Kusztal
This patch removes information about deprecation of AES-GCM/GMAC
API for IV without J0.
J0 was added with the following patch:
- cryptodev: add an option to support both iv and J0 for GCM [1]
[1] (http://patchwork.dpdk.org/patch/52886/)
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
v2:
- added reference to the patch in question
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 f9b72acb8..281f38048 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -235,12 +235,6 @@ Deprecation Notices
``RTE_CRYPTO_AUTH_LIST_END`` from ``enum rte_crypto_auth_algorithm``
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.
-
* scheduler: The functions ``rte_cryptodev_scheduler_slave_attach``,
``rte_cryptodev_scheduler_slave_detach`` and
``rte_cryptodev_scheduler_slaves_get`` will be replaced in 20.11 by
--
2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-10-28 11:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-14 5:07 [dpdk-dev] [PATCH v2] doc: remove aes-gcm addition of j0 deprecation notice Arek Kusztal
2020-10-28 11:14 ` Akhil Goyal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).