From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: replace wireless algos test vectors
Date: Mon, 17 Feb 2020 10:49:54 +0000 [thread overview]
Message-ID: <BN6PR11MB1796379AC00678D1B9C27D87E4160@BN6PR11MB1796.namprd11.prod.outlook.com> (raw)
In-Reply-To: <522B1A062D56224ABC0C6BDBCD64D9D38CB24FC9@irsmsx105.ger.corp.intel.com>
Hi Akhil, Thomas,
Can you please hold off on applying this patch for the moment - it seems we may get approval on licensing for the original vectors.
Fiona
> -----Original Message-----
> From: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Sent: Thursday, February 13, 2020 1:44 PM
> To: Akhil Goyal <akhil.goyal@nxp.com>; dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>
> Subject: RE: [dpdk-dev] [PATCH] test/crypto: replace wireless algos test vectors
>
> 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
> >
>
next prev parent reply other threads:[~2020-02-17 10:49 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
2020-02-17 10:49 ` Trahe, Fiona [this message]
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=BN6PR11MB1796379AC00678D1B9C27D87E4160@BN6PR11MB1796.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/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).