DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"Trahe,  Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: replace wireless algos test vectors
Date: Thu, 13 Feb 2020 13:44:16 +0000	[thread overview]
Message-ID: <522B1A062D56224ABC0C6BDBCD64D9D38CB24FC9@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <VE1PR04MB66398F585001CDF8DAF0B7C1E61B0@VE1PR04MB6639.eurprd04.prod.outlook.com>

Hi.

The reason for changing these vectors is the same as for a bit similar Artur's compression vectors change patch: http://patches.dpdk.org/patch/65616/
Basically speaking, we'd like to remove everything with unclear license. To do that, I replaced all wireless crypto (SNOW3G, ZUC, KASUMI etc) algorithms' test vectors (input arrays) with completely randomized data.

Outputs for the test vectors were calculated using Intel's QuickAssist PMD and software-only PMDs (sw_snow3g, sw_zuc etc), and cross-checked to ensure all unit tests are passing correctly. I hope this answers your question about the interoperability.

This patch changes unit test vectors only. No internal PMDs' code has been changed so it won't affect other applications that use DPDK.

It'll be great of course if anyone can verify whether new unit tests pass correctly on other hardware-based PMDs that can handle wireless algorithms like OcteonTX / DPAA / DPAA2.

Adam

> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Wednesday, 12 February, 2020 14:23
> To: Dybkowski, AdamX <adamx.dybkowski@intel.com>; dev@dpdk.org;
> Trahe, Fiona <fiona.trahe@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] test/crypto: replace wireless algos test
> vectors
> 
> Hi Adam/Fiona,
> >
> > This patch replaces all KASUMI, SNOW3G, ZUC and all mixed crypto unit
> > test vectors with randomly generated input arrays.
> > All outputs were calculated and verified on both QAT PMD and
> > appropriate software-only PMDs wherever possible.
> >
> > Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> > ---
> I have few doubts about this patch
> 
> -> What is the reason for changing the test vectors?
> -> Are these based on some standard test vectors somewhere?
> -> Have you done any interoperability tests on these vectors?
> 
> Regards,
> Akhil
> 


  reply	other threads:[~2020-02-13 13:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 11:24 Adam Dybkowski
2020-02-07  9:29 ` Trahe, Fiona
2020-02-12 13:23 ` Akhil Goyal
2020-02-13 13:44   ` Dybkowski, AdamX [this message]
2020-02-17 10:49     ` Trahe, Fiona
2020-04-01 14:14       ` Akhil Goyal
2020-04-02 12:37         ` Mcnamara, John

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=522B1A062D56224ABC0C6BDBCD64D9D38CB24FC9@irsmsx105.ger.corp.intel.com \
    --to=adamx.dybkowski@intel.com \
    --cc=akhil.goyal@nxp.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).