From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fiona Trahe <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
"adamx.dybkowski@intel.com" <adamx.dybkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] cryptodev: clarify wireless inputs in digest-encrypted cases
Date: Tue, 22 Oct 2019 13:24:22 +0000 [thread overview]
Message-ID: <VE1PR04MB66393CAD857E057544DB70ACE6680@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1571750416-11742-1-git-send-email-fiona.trahe@intel.com>
>
> Clarify constraints on fields specified in bits for wireless
> algorithms in digest-encrypted case.
>
> v2 changes:
> - added note on each of the affected parameter fields
>
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
> lib/librte_cryptodev/rte_crypto_sym.h | 23 +++++++++++++++++++----
> 1 files changed, 19 insertions(+), 4 deletions(-)
>
//snip//
> @@ -703,6 +711,13 @@ struct rte_crypto_sym_op {
> * auth.data.length and is typically
> * equal to auth.data.offset +
> * auth.data.length + digest_length.
> + * - for wireless algorithms, i.e.
> + * SNOW 3G, KASUMI and ZUC, as the
> + * cipher.data.length,
> + * cipher.data.offset,
> + * auth.data.length and
> + * auth.data.offset are in bits, they
> + * must be 8-bit multiples.
Why do you need this change? This is redundant information.
> *
> * Note, that for security reasons, it
> * is PMDs' responsibility to not
> --
> 1.7.0.7
next prev parent reply other threads:[~2019-10-22 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 11:34 [dpdk-dev] [PATCH] " Fiona Trahe
2019-10-22 11:48 ` Akhil Goyal
2019-10-22 12:00 ` Trahe, Fiona
2019-10-22 12:08 ` Akhil Goyal
2019-10-22 12:32 ` Trahe, Fiona
2019-10-22 13:20 ` [dpdk-dev] [PATCH v2] " Fiona Trahe
2019-10-22 13:24 ` Akhil Goyal [this message]
2019-10-22 14:46 ` Trahe, Fiona
2019-10-23 14: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=VE1PR04MB66393CAD857E057544DB70ACE6680@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=adamx.dybkowski@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
/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).