From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: declan.doherty@intel.com, fiona.trahe@intel.com,
john.griffin@intel.com, deepak.k.jain@intel.com
Cc: dev@dpdk.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>,
stable@dpdk.org
Subject: [dpdk-dev] [PATCH 4/5] doc: add missing algorithm in limitations for QAT
Date: Thu, 13 Jul 2017 06:36:49 +0100 [thread overview]
Message-ID: <20170713053650.62998-5-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <20170713053650.62998-1-pablo.de.lara.guarch@intel.com>
For KASUMI, SNOW3G and ZUC algorithms, offsets and lengths
of the data to cipher or authenticate is provided in bits,
but QAT does not support non-byte aligned values,
although only KASUMI and SNOW3G were mentioned.
Fixes: d9b7d5bbc845 ("crypto/qat: add ZUC EEA3/EIA3 capability")
Cc: stable@dpdk.org
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
doc/guides/cryptodevs/qat.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
index 7a510c9..8e390ee 100644
--- a/doc/guides/cryptodevs/qat.rst
+++ b/doc/guides/cryptodevs/qat.rst
@@ -85,8 +85,8 @@ Limitations
-----------
* Only supports the session-oriented API implementation (session-less APIs are not supported).
-* SNOW 3G (UEA2) and KASUMI (F8) supported only if cipher length, cipher offset fields are byte-aligned.
-* SNOW 3G (UIA2) and KASUMI (F9) supported only if hash length, hash offset fields are byte-aligned.
+* SNOW 3G (UEA2), KASUMI (F8) and ZUC (EEA3) supported only if cipher length, cipher offset fields are byte-aligned.
+* SNOW 3G (UIA2), KASUMI (F9) and ZUC (EIA3) supported only if hash length, hash offset fields are byte-aligned.
* No BSD support as BSD QAT kernel driver not available.
* ZUC EEA3/EIA3 is not supported by dh895xcc devices
* Maximum additional authenticated data (AAD) for GCM is 240 bytes long.
--
2.9.4
next prev parent reply other threads:[~2017-07-13 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 5:36 [dpdk-dev] [PATCH 0/5] Fix crypto PMDs documentation Pablo de Lara
2017-07-13 5:36 ` [dpdk-dev] [PATCH 1/5] doc: fix supported algorithm table for AESNI GCM PMD Pablo de Lara
2017-07-13 5:36 ` [dpdk-dev] [PATCH 2/5] doc: remove incorrect limitation on QAT PMD Pablo de Lara
2017-07-14 15:58 ` Trahe, Fiona
2017-07-13 5:36 ` [dpdk-dev] [PATCH 3/5] doc: remove incorrect limitation on AESNI MB PMD Pablo de Lara
2017-07-13 5:36 ` Pablo de Lara [this message]
2017-07-14 16:13 ` [dpdk-dev] [PATCH 4/5] doc: add missing algorithm in limitations for QAT Trahe, Fiona
2017-07-13 5:36 ` [dpdk-dev] [PATCH 5/5] doc: extend installation section on SNOW3G/KASUMI PMDs Pablo de Lara
2017-07-13 17:00 ` [dpdk-dev] [PATCH 0/5] Fix crypto PMDs documentation Declan Doherty
2017-07-16 10:52 ` De Lara Guarch, Pablo
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=20170713053650.62998-5-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@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).