From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] doc/qat: add GCM AAD limitation
Date: Fri, 18 Jan 2019 12:26:55 +0000 [thread overview]
Message-ID: <06EE24DD0B19E248B53F6DC8657831551B12C9F4@hasmsx109.ger.corp.intel.com> (raw)
In-Reply-To: <1547749399-1975-1-git-send-email-fiona.trahe@intel.com>
> -----Original Message-----
> From: Trahe, Fiona
> Sent: Thursday, January 17, 2019 7:23 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>; akhil.goyal@nxp.com; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>; stable@dpdk.org
> Subject: [PATCH] doc/qat: add GCM AAD limitation
>
> 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 <fiona.trahe@intel.com>
> ---
> doc/guides/cryptodevs/qat.rst | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
> index 9fb9f01..3ca70bc 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
> ~~~~~~~~~~~~~~~~~~~~~~~~
>
> --
> 1.7.0.7
Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
next prev parent reply other threads:[~2019-01-18 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 18:23 Fiona Trahe
2019-01-18 12:26 ` Kusztal, ArkadiuszX [this message]
2019-01-20 14:11 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=06EE24DD0B19E248B53F6DC8657831551B12C9F4@hasmsx109.ger.corp.intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).