From: Akhil Goyal <gakhil@marvell.com>
To: David Marchand <david.marchand@redhat.com>,
Vidya Sagar Velumuri <vvelumuri@marvell.com>
Cc: dev <dev@dpdk.org>, "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [EXT] Re: [Bug 828] [dpdk-21.11] zuc unit test is failing
Date: Fri, 15 Oct 2021 18:04:41 +0000 [thread overview]
Message-ID: <CO6PR18MB448421225C509AE27A9EAF38D8B99@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8y8-E4H3Npt9M2df+5NRhWyV=js=4qG0Pvb1DydhKeADA@mail.gmail.com>
> Hello,
>
> On Fri, Oct 15, 2021 at 10:02 AM <bugzilla@dpdk.org> wrote:
> >
> > https://bugs.dpdk.org/show_bug.cgi?id=828
> >
> > Bug ID: 828
> > Summary: [dpdk-21.11] zuc unit test is failing
> > Product: DPDK
> > Version: 21.11
> > Hardware: All
> > OS: Linux
> > Status: UNCONFIRMED
> > Severity: normal
> > Priority: Normal
> > Component: cryptodev
> > Assignee: dev@dpdk.org
> > Reporter: varalakshmi.s@intel.com
> > Target Milestone: ---
>
> I could not assign this bug to you in bz, can you have a look?
> Thanks.
>
Can somebody from Intel look into this?
We don’t have intel-ipsec-mb library access, so cannot reproduce the issue.
The test case is passing on cnxk hardware. Please let us know if the vectors
added in the patch are not correct.
>
> >
> > Steps to reproduce
> >
> > from dpdk path, the following steps should be followed:
> > x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1,2,3 --vdev crypto_zuc0
> > --socket-mem 2048,0 -n 4 --log-level=6 -a 0000:1a:01.0
> >
> > RTE>> cryptodev_sw_zuc_autotest
> >
>
> [snip]
>
> > + ------------------------------------------------------- +
> > + Sub Testsuites Total : 27
> > + Sub Testsuites Skipped : 25
> > + Sub Testsuites Passed : 1
> > + Sub Testsuites Failed : 1
> > + ------------------------------------------------------- +
> > + Tests Total : 511
> > + Tests Skipped : 488
> > + Tests Executed : 65
> > + Tests Unsupported: 0
> > + Tests Passed : 20
> > + Tests Failed : 3
> > + ------------------------------------------------------- +
> > Test Failed
> > RTE>>
> >
>
> > ----------------------------------------------------------------
> > fa5bf9345d4e0141ac40f154b1c1a4b99e8fe9a3 is the first bad commit
> >
> > commit fa5bf9345d4e0141ac40f154b1c1a4b99e8fe9a3
> > Author: Vidya Sagar Velumuri <vvelumuri@marvell.com>
> > Date: Wed Sep 15 06:11:03 2021 +0000
> >
> > test/crypto: add ZUC cases with 256-bit keys
> >
> > Add test cases for zuc 256 bit key.
> > Add test case for zuc 8 and 16 byte digest with
> > 256 bit key mode
> >
> > Signed-off-by: Vidya Sagar Velumuri <vvelumuri@marvell.com>
> > Acked-by: Akhil Goyal <gakhil@marvell.com>
>
>
>
> --
> David Marchand
next prev parent reply other threads:[~2021-10-15 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 8:02 [dpdk-dev] " bugzilla
2021-10-15 8:14 ` David Marchand
2021-10-15 18:04 ` Akhil Goyal [this message]
2021-10-16 5:04 ` [dpdk-dev] [EXT] " Vidya Sagar Velumuri
2021-10-16 13:10 ` Zhang, Roy Fan
2021-10-18 7:46 ` David Marchand
2021-10-18 21:42 ` 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=CO6PR18MB448421225C509AE27A9EAF38D8B99@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=vvelumuri@marvell.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).