From: Fiona Trahe <fiona.trahe@intel.com>
To: stable@dpdk.org, pablo.de.lara.guarch@intel.com
Cc: deepak.k.jain@intel.com, fiona.trahe@intel.com
Subject: [dpdk-stable] [PATCH] doc: fix crypto overview matrix for missing QAT items
Date: Fri, 3 Mar 2017 16:34:22 +0000 [thread overview]
Message-ID: <1488558862-13376-1-git-send-email-fiona.trahe@intel.com> (raw)
Support for all the following was added in release 16.11
but not updated in the matrix:
3DES, MD5_HMAC, SHA224, SHA383, NULL, KASUMI F8/F9, GMAC.
Fixes: e1b7f509e6f2 ("crypto/qat: add 3DES cipher algorithm")
Fixes: 61ec5181625f ("crypto/qat: add MD5 HMAC capability")
Fixes: ebdbe12fbfc1 ("crypto/qat: add aes-sha224-hmac capability")
Fixes: d905ee32d0dc ("crypto/qat: add aes-sha384-hmac capability")
Fixes: db0e952a5c01 ("crypto/qat: add NULL capability")
Fixes: d4f2745300e0 ("crypto/qat: add KASUMI")
Fixes: 2fa64f840d65 ("crypto/qat: add GMAC capability")
Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
---
This patch is backported for 16.11 next stable release
doc/guides/cryptodevs/overview.rst | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index d612f71..e6dfffc 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -51,15 +51,17 @@ Supported Cipher Algorithms
:header: "Cipher Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi"
:stub-columns: 1
- "NULL",,x,,,,
+ "NULL",x,x,,,,
"AES_CBC_128",x,,x,,,
"AES_CBC_192",x,,x,,,
"AES_CBC_256",x,,x,,,
"AES_CTR_128",x,,x,,,
"AES_CTR_192",x,,x,,,
"AES_CTR_256",x,,x,,,
+ "3DES_CTR",x,,,,,
+ "3DES_CTR",x,,,,,
"SNOW3G_UEA2",x,,,,x,
- "KASUMI_F8",,,,,,x
+ "KASUMI_F8",x,,,,,x
Supported Authentication Algorithms
@@ -67,22 +69,23 @@ Supported Authentication Algorithms
:header: "Cipher Algorithms", "qat", "null", "aesni_mb", "aesni_gcm", "snow3g", "kasumi"
:stub-columns: 1
- "NONE",,x,,,,
+ "NULL",x,x,,,,
"MD5",,,,,,
- "MD5_HMAC",,,x,,,
+ "MD5_HMAC",x,,x,,,
"SHA1",,,,,,
"SHA1_HMAC",x,,x,,,
"SHA224",,,,,,
- "SHA224_HMAC",,,x,,,
+ "SHA224_HMAC",x,,x,,,
"SHA256",,,,,,
"SHA256_HMAC",x,,x,,,
"SHA384",,,,,,
- "SHA384_HMAC",,,x,,,
+ "SHA384_HMAC",x,,x,,,
"SHA512",,,,,,
"SHA512_HMAC",x,,x,,,
"AES_XCBC",x,,x,,,
+ "AES_GMAC",x,,,,,
"SNOW3G_UIA2",x,,,,x,
- "KASUMI_F9",,,,,,x
+ "KASUMI_F9",x,,,,,x
Supported AEAD Algorithms
--
2.5.0
next reply other threads:[~2017-03-03 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:34 Fiona Trahe [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-03 16:21 Fiona Trahe
2017-03-03 12:51 Fiona Trahe
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=1488558862-13376-1-git-send-email-fiona.trahe@intel.com \
--to=fiona.trahe@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
/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).