All of lore.kernel.org
 help / color / mirror / Atom feed
From: Archana Muniganti <marchana@marvell.com>
To: Akhil Goyal <gakhil@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:21:21 +0000	[thread overview]
Message-ID: <PH0PR18MB402320B85A86DA8CC07A6390C3FC9@PH0PR18MB4023.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB44847040F2E9B664A65C877CD8FC9@CO6PR18MB4484.namprd18.prod.outlook.com>

Hi Akhil,

Please see inline.

Thanks,
Archana

> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Friday, April 29, 2022 11:31 AM
> To: Archana Muniganti <marchana@marvell.com>; ciara.power@intel.com;
> declan.doherty@intel.com
> Cc: Archana Muniganti <marchana@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>; dev@dpdk.org
> 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.

  reply	other threads:[~2022-04-29  9:21 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 [this message]
2022-04-29  9:31       ` 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=PH0PR18MB402320B85A86DA8CC07A6390C3FC9@PH0PR18MB4023.namprd18.prod.outlook.com \
    --to=marchana@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.