dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Shally Verma <shallyv@marvell.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	Ayuj Verma <ayverma@marvell.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	 Sunila Sahu <ssahu@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"Kanaka Durga Kotamarthy" <kkotamarthy@marvell.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1 0/2] add tests for RSA key type CRT
Date: Mon, 15 Jul 2019 10:05:49 +0000	[thread overview]
Message-ID: <275ea79e-45ce-435e-b647-793e6b253cfb@marvell.com> (raw)

Thanks Arek. Response inline.

Sent from Workspace ONE Boxer
On 12-Jul-2019 6:45 PM, "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com> wrote:
>
> In future we could unify tests even more (i.e. passing padding type as a param, or even information if it is encryption or signature generation) like Fan once done with blockcipher.

I will take a look at that but isn't test suite preferable otherwise? Means keeping it less interactive in nature? Else command line args will be different combinations of padding type, modulus length, crt/non-crt, op type ..is it okay to make it this way?

Thanks
Shally

>
> > -----Original Message-----
> > From: Ayuj Verma [mailto:ayverma@marvell.com]
> > Sent: Thursday, July 11, 2019 3:23 PM
> > To: akhil.goyal@nxp.com
> > Cc: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; Trahe, Fiona
> > <fiona.trahe@intel.com>; shallyv@marvell.com; ssahu@marvell.com;
> > kkotamarthy@marvell.com; anoobj@marvell.com; dev@dpdk.org; Ayuj
> > Verma <ayverma@marvell.com>
> > Subject: [PATCH v1 0/2] add tests for RSA key type CRT
> >
> > This patch series add new RSA CRT key based test cases, improve code
> > organization and also rebase it to latest changes.
> > It covers following changes:
> >
> > * Add crt key based rsa sign/verify, enc/decrypt test cases
> > * Move common code of enqueue/dequeue into separate function
> > * Configure device with ff_disable set
> >
> > Ayuj Verma (2):
> >   test/crypto: move rsa enqueue/dequeue into separate functions
> >   test/crypto: add tests for RSA key type CRT
> >
> >  app/test/test_cryptodev_asym.c             | 460 +++++++++++++++++------------
> >  app/test/test_cryptodev_rsa_test_vectors.h |  93 ++++++
> >  2 files changed, 363 insertions(+), 190 deletions(-)
> >
> > --
> > 1.8.3.1
>
> Series-acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
>


             reply	other threads:[~2019-07-15 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 10:05 Shally Verma [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-16 12:04 [dpdk-dev] [PATCH v1 0/2] add tests for RSA key type CRT Shally Verma
2019-07-18 15:35 ` Akhil Goyal
2019-07-11 13:22 Ayuj Verma
2019-07-12 13:15 ` 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=275ea79e-45ce-435e-b647-793e6b253cfb@marvell.com \
    --to=shallyv@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ayverma@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=kkotamarthy@marvell.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=ssahu@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).