From 2a7bb4fdf61e9edfb7adbaecb50e728b82da9e23 Mon Sep 17 00:00:00 2001 From: Fiona Trahe Date: Thu, 17 Jan 2019 18:23:19 +0000 Subject: [PATCH] doc: add GCM AAD limitation in qat guide Add limitation that AAD buffer must be padded with zeroes in GCM case. Fixes: d4f44265a1d7 ("doc: add limitation of AAD size to QAT guide") Cc: stable@dpdk.org Signed-off-by: Fiona Trahe Acked-by: Arek Kusztal --- doc/guides/cryptodevs/qat.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst index 9fb9f01d1e..3ca70bc05c 100644 --- a/doc/guides/cryptodevs/qat.rst +++ b/doc/guides/cryptodevs/qat.rst @@ -79,10 +79,9 @@ Limitations * SNOW 3G (UIA2) 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. +* Maximum additional authenticated data (AAD) for GCM is 240 bytes long and must be passed to the device in a buffer rounded up to the nearest block-size multiple (x16) and padded with zeros. * Queue pairs are not thread-safe (that is, within a single queue pair, RX and TX from different lcores is not supported). - Extra notes on KASUMI F9 ~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.20.1