DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Archana Muniganti <marchana@marvell.com>,
	"ciara.power@intel.com" <ciara.power@intel.com>,
	"declan.doherty@intel.com" <declan.doherty@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 2/2] app/crypto-perf: add vector file for AES-GCM
Date: Fri, 29 Apr 2022 09:31:17 +0000	[thread overview]
Message-ID: <CO6PR18MB4484C8943DE6D02BFD6CB533D8FC9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB402320B85A86DA8CC07A6390C3FC9@PH0PR18MB4023.namprd18.prod.outlook.com>

> > Subject: RE: [PATCH 2/2] app/crypto-perf: add vector file for AES-GCM
> >
> > > Subject: [PATCH 2/2] app/crypto-perf: add vector file for AES-GCM
> > >
> > > Added test vector file for AES-128-GCM for 64B and 512B length
> > > buffers.
> > >
> > > Signed-off-by: Archana Muniganti <marchana@marvell.com>
> > From where are these vectors taken?
> [Archana] The test vectors are self generated from a fips complaint device.

OK
Acked-by: Akhil Goyal <gakhil@marvell.com>


      reply	other threads:[~2022-04-29  9:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 10:18 [PATCH 0/2] populate mbuf in latency test Archana Muniganti
2022-04-08 10:18 ` [PATCH 1/2] app/crypto-perf: " Archana Muniganti
2022-04-29  5:59   ` Akhil Goyal
2022-04-29  9:35     ` Akhil Goyal
2022-04-08 10:18 ` [PATCH 2/2] app/crypto-perf: add vector file for AES-GCM Archana Muniganti
2022-04-29  6:01   ` Akhil Goyal
2022-04-29  9:21     ` Archana Muniganti
2022-04-29  9:31       ` Akhil Goyal [this message]

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=CO6PR18MB4484C8943DE6D02BFD6CB533D8FC9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=marchana@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).