From: Anoob Joseph <anoobj@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
Akhil Goyal <gakhil@marvell.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Cc: Umesh Kartha <ukartha@marvell.com>,
Ramkumar Balu <rbalu@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH] test/crypto: remove mod exp smaller modulus cases
Date: Wed, 23 Feb 2022 15:17:45 +0000 [thread overview]
Message-ID: <PH0PR18MB4672A1DAFC15F6C4FCC0431EDF3C9@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB580983E0BF8D2702EE816FCBB83C9@MW5PR11MB5809.namprd11.prod.outlook.com>
Hi Fan, Akhil,
In that case, I don't think there is any other alternative than what Fan suggested (remove it now and add back along with capabilities). No objections to that from my end. Leaving that to Akhil's judgement.
I would still prefer adding a driver specific check, though.
Thanks,
Anoob
> -----Original Message-----
> From: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Sent: Wednesday, February 23, 2022 8:22 PM
> To: Akhil Goyal <gakhil@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Cc: Umesh Kartha <ukartha@marvell.com>; Ramkumar Balu
> <rbalu@marvell.com>; dev@dpdk.org
> Subject: RE: [EXT] [PATCH] test/crypto: remove mod exp smaller modulus
> cases
>
> Hi Akhil,
>
> Currently these tests will fail on QAT - is it possible to merge this patch so that
> QAT won't fail and we can add them back after the capability check is added
> in the next release?
>
> Regards,
> Fan
>
> > -----Original Message-----
> > From: Akhil Goyal <gakhil@marvell.com>
> > Sent: Wednesday, February 23, 2022 2:38 PM
> > To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; Anoob Joseph
> > <anoobj@marvell.com>; Kusztal, ArkadiuszX
> > <arkadiuszx.kusztal@intel.com>
> > Cc: Umesh Kartha <ukartha@marvell.com>; Ramkumar Balu
> > <rbalu@marvell.com>; dev@dpdk.org
> > Subject: RE: [EXT] [PATCH] test/crypto: remove mod exp smaller modulus
> > cases
> >
> > Hi Anoob/Fan,
> > We no more add driver specific checks in test app. Everything comes
> > from capabilities.
> > We may defer this patch to next release till we have something in
> > capability or some other way.
> >
> > > Hi Anoob,
> > >
> > > Make sense. Will do ASAP.
> > >
> > > Regards,
> > > Fan
> > >
next prev parent reply other threads:[~2022-02-23 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 10:54 Arek Kusztal
2022-02-23 10:09 ` [EXT] " Anoob Joseph
2022-02-23 10:34 ` Zhang, Roy Fan
2022-02-23 13:28 ` Anoob Joseph
2022-02-23 14:28 ` Zhang, Roy Fan
2022-02-23 14:37 ` Akhil Goyal
2022-02-23 14:52 ` Zhang, Roy Fan
2022-02-23 15:17 ` Anoob Joseph [this message]
2022-03-01 8:37 ` Kusztal, ArkadiuszX
2022-03-01 15:14 ` Kusztal, ArkadiuszX
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=PH0PR18MB4672A1DAFC15F6C4FCC0431EDF3C9@PH0PR18MB4672.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=rbalu@marvell.com \
--cc=roy.fan.zhang@intel.com \
--cc=ukartha@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).