From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: akhil.goyal@nxp.com, fiona.trahe@intel.com,
pablo.de.lara.guarch@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH] doc: add cryptodev gcm iv deprecation notice
Date: Wed, 17 Apr 2019 09:41:13 +0200 [thread overview]
Message-ID: <20190417074113.10896-1-arkadiuszx.kusztal@intel.com> (raw)
Message-ID: <20190417074113.SFyclZ30kBzc8yfTTGdhGHjTcu_NoxjE39woX9OAvtM@z> (raw)
This patch adds deprecation notice of changing iv behaviour
when using Galois Counter Mode of operation. Right now IV of
all supported sizes can be used.
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ba39c2d..76eb166 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -87,3 +87,9 @@ Deprecation Notices
* cryptodev: the ``uint8_t *data`` member of ``key`` structure in the xforms
structure (``rte_crypto_cipher_xform``, ``rte_crypto_auth_xform``, and
``rte_crypto_aead_xform``) will be changed to ``const uint8_t *data``.
+
+* 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.
--
2.1.0
next reply other threads:[~2019-04-17 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 7:41 Arek Kusztal [this message]
2019-04-17 7:41 ` Arek Kusztal
2019-04-17 11:32 ` Trahe, Fiona
2019-04-17 11:32 ` Trahe, Fiona
2019-05-13 21:25 ` Thomas Monjalon
2019-05-13 21:25 ` Thomas Monjalon
2019-05-08 8:23 ` De Lara Guarch, Pablo
2019-05-08 8:23 ` De Lara Guarch, Pablo
2019-05-09 9:03 ` Akhil Goyal
2019-05-09 9:03 ` Akhil Goyal
2019-05-09 11:31 ` Anoob Joseph
2019-05-09 11:31 ` Anoob Joseph
2019-04-30 6:59 Akhil Goyal
2019-04-30 6:59 ` Akhil Goyal
2019-05-03 18:09 ` Trahe, Fiona
2019-05-03 18:09 ` Trahe, Fiona
2019-05-04 18:06 ` Liron Himi
2019-05-04 18:06 ` Liron Himi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190417074113.10896-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).