DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Weqaar Janjua <Weqaar.A.Janjua@intel.com>,
	John Griffin <john.griffin@intel.com>
Subject: Re: [dpdk-dev] [dpdk-dev v3 2/2] fips_validation: update GCM test
Date: Sat, 10 Oct 2020 16:55:50 +0000	[thread overview]
Message-ID: <VI1PR04MB31683FC20480B0BEED414267E6090@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201009200822.4652-3-roy.fan.zhang@intel.com>

> This patch updates fips validation GCM test capabilities:
> 
> - In NIST GCMVS spec GMAC test vectors are the GCM ones with
> plaintext length as 0 and uses AAD as input data. Originally
> fips_validation tests treats them both as GCM test vectors.
> This patch introduce automatic test type recognition between
> the two: when plaintext length is 0 the prepare_gmac_xform
> and prepare_auth_op functions are called, otherwise
> prepare_gcm_xform and prepare_aead_op functions are called.
> 
> - NIST GCMVS also specified externally or internally IV
> generation. When IV is to be generated by IUT internally IUT
> shall store the generated IV in the response file. This patch
> also adds the support to that.
> 
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> Signed-off-by: Weqaar Janjua <Weqaar.A.Janjua@intel.com>
> Acked-by: John Griffin <john.griffin@intel.com>
> ---
>  doc/guides/rel_notes/release_20_11.rst        |   5 +
>  examples/fips_validation/fips_validation.h    |  26 ++++
>  .../fips_validation/fips_validation_gcm.c     | 118 ++++++++++++++++--
>  examples/fips_validation/main.c               |  65 ++++++++--
>  4 files changed, 189 insertions(+), 25 deletions(-)
> 
> diff --git a/doc/guides/rel_notes/release_20_11.rst
> b/doc/guides/rel_notes/release_20_11.rst
> index 059ea5fca..7441e6ce4 100644
> --- a/doc/guides/rel_notes/release_20_11.rst
> +++ b/doc/guides/rel_notes/release_20_11.rst
> @@ -159,6 +159,11 @@ New Features
>    * Extern objects and functions can be plugged into the pipeline.
>    * Transaction-oriented table updates.
> 
> +* **fips_validation sample application enhancement.**
> +
> +     fips_vadation sample application is added SGL and NIST GCMVS complaint
> +     GMAC test method support.
> +
> 
These release notes need to be split into two for both the patches in the list. 
I did it while applying the patches.

Series Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2020-10-10 16:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 12:17 [dpdk-dev] [dpdk-dev 0/2] fips_validation: add SGL and GMAC support Fan Zhang
2020-08-18 12:17 ` [dpdk-dev] [dpdk-dev 1/2] fips_validation: add SGL support Fan Zhang
2020-08-18 12:17 ` [dpdk-dev] [dpdk-dev 2/2] fips_validation: update GCM test Fan Zhang
2020-09-04 16:09 ` [dpdk-dev] [dpdk-dev v2 0/2] fips_validation: add SGL and GMAC support Fan Zhang
2020-09-04 16:09   ` [dpdk-dev] [dpdk-dev v2 1/2] fips_validation: add SGL support Fan Zhang
2020-09-07 13:32     ` Suanming Mou
2020-09-08 10:13       ` Zhang, Roy Fan
2020-09-17  9:20     ` Griffin, John
2020-09-04 16:09   ` [dpdk-dev] [dpdk-dev v2 2/2] fips_validation: update GCM test Fan Zhang
2020-09-17  9:20     ` Griffin, John
2020-10-09 18:23   ` [dpdk-dev] [dpdk-dev v2 0/2] fips_validation: add SGL and GMAC support Akhil Goyal
2020-10-09 18:47     ` Zhang, Roy Fan
2020-10-09 20:08   ` [dpdk-dev] [dpdk-dev v3 " Fan Zhang
2020-10-09 20:08     ` [dpdk-dev] [dpdk-dev v3 1/2] fips_validation: add SGL support Fan Zhang
2020-10-09 20:08     ` [dpdk-dev] [dpdk-dev v3 2/2] fips_validation: update GCM test Fan Zhang
2020-10-10 16:55       ` Akhil Goyal [this message]

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=VI1PR04MB31683FC20480B0BEED414267E6090@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=Weqaar.A.Janjua@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.griffin@intel.com \
    --cc=roy.fan.zhang@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).