From: Pablo de Lara Date: Thu, 13 Jul 2017 05:36:49 +0000 (+0100) Subject: doc: add missing algorithm in limitations for QAT X-Git-Tag: spdx-start~2401 X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=2142e6dc71b46d1ff4cd03c12a0153e30d3a1fa3;p=dpdk.git doc: add missing algorithm in limitations for QAT 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 Acked-by: Declan Doherty --- diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst index 7a510c99aa..6320c66477 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 and offset fields are byte-multiple. +* SNOW 3G (UIA2), KASUMI (F9) and ZUC (EIA3) supported only if hash length and offset fields are byte-multiple. * 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.