From: Tomasz Cel <tomaszx.cel@intel.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, fiona.trahe@intel.com, akhil.goyal@nxp.com,
marko.kovacevic@intel.com, arkadiuszx.kusztal@intel.com,
mattias.ronnblom@ericsson.com, Tomasz Cel <tomaszx.cel@intel.com>
Subject: [dpdk-dev] [PATCH v4 3/3] doc/qat: update AES-CMAC documentation
Date: Tue, 9 Oct 2018 18:08:12 +0200 [thread overview]
Message-ID: <1539101292-18984-4-git-send-email-tomaszx.cel@intel.com> (raw)
In-Reply-To: <1539101292-18984-1-git-send-email-tomaszx.cel@intel.com>
Update the QAT documentation to show that it supports AES-CMAC.
Signed-off-by: Tomasz Cel <tomaszx.cel@intel.com>
---
doc/guides/cryptodevs/features/qat.ini | 1 +
doc/guides/cryptodevs/qat.rst | 1 +
doc/guides/rel_notes/release_18_11.rst | 6 ++++++
3 files changed, 8 insertions(+)
diff --git a/doc/guides/cryptodevs/features/qat.ini b/doc/guides/cryptodevs/features/qat.ini
index 220291b..4f15ee0 100644
--- a/doc/guides/cryptodevs/features/qat.ini
+++ b/doc/guides/cryptodevs/features/qat.ini
@@ -48,6 +48,7 @@ SNOW3G UIA2 = Y
KASUMI F9 = Y
AES XCBC MAC = Y
ZUC EIA3 = Y
+AES CMAC (128) = Y
;
; Supported AEAD algorithms of the 'qat' crypto driver.
diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
index b09624f..d1d4833 100644
--- a/doc/guides/cryptodevs/qat.rst
+++ b/doc/guides/cryptodevs/qat.rst
@@ -62,6 +62,7 @@ Hash algorithms:
* ``RTE_CRYPTO_AUTH_KASUMI_F9``
* ``RTE_CRYPTO_AUTH_AES_GMAC``
* ``RTE_CRYPTO_AUTH_ZUC_EIA3``
+* ``RTE_CRYPTO_AUTH_AES_CMAC``
Supported AEAD algorithms:
diff --git a/doc/guides/rel_notes/release_18_11.rst b/doc/guides/rel_notes/release_18_11.rst
index 2133a5b..18a39a8 100644
--- a/doc/guides/rel_notes/release_18_11.rst
+++ b/doc/guides/rel_notes/release_18_11.rst
@@ -72,6 +72,12 @@ New Features
SR-IOV option in Hyper-V and Azure. This is an alternative to the previous
vdev_netvsc, tap, and failsafe drivers combination.
+* **Updated the QAT PMD.**
+
+ The QAT PMD was updated with additional support for:
+
+ * AES-CMAC algorithm.
+
* **Updated failsafe driver.**
Updated the failsafe driver including the following changes:
--
2.7.4
next prev parent reply other threads:[~2018-10-09 16:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 18:10 [dpdk-dev] [PATCH 0/3] add AES-CMAC support Tomasz Cel
2018-09-28 18:10 ` [dpdk-dev] [PATCH 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-09-28 18:10 ` [dpdk-dev] [PATCH 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-09-28 18:10 ` [dpdk-dev] [PATCH 3/3] doc/qat: add AES-CMAC to the QAT feature list Tomasz Cel
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 0/3] add AES-CMAC support Tomasz Cel
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-10-05 12:02 ` Mattias Rönnblom
2018-10-05 13:27 ` Trahe, Fiona
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 3/3] doc/qat: add AES-CMAC to the QAT feature list Tomasz Cel
2018-10-04 11:47 ` [dpdk-dev] [PATCH v2 0/3] add AES-CMAC support Trahe, Fiona
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 " Tomasz Cel
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 3/3] doc/qat: update AES-CMAC documentation Tomasz Cel
2018-10-09 14:37 ` Trahe, Fiona
2018-10-09 16:08 ` [dpdk-dev] [PATCH v4 0/3] add AES-CMAC support Tomasz Cel
2018-10-09 16:08 ` [dpdk-dev] [PATCH v4 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-10-09 16:08 ` [dpdk-dev] [PATCH v4 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-10-09 16:08 ` Tomasz Cel [this message]
2018-10-09 16:25 ` [dpdk-dev] [PATCH v4 0/3] add AES-CMAC support Trahe, Fiona
2018-10-10 10:59 ` Akhil Goyal
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=1539101292-18984-4-git-send-email-tomaszx.cel@intel.com \
--to=tomaszx.cel@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=mattias.ronnblom@ericsson.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).