DPDK patches and discussions
 help / color / mirror / Atom feed
From: Archana Muniganti <marchana@marvell.com>
To: <ciara.power@intel.com>, <declan.doherty@intel.com>,
	<gakhil@marvell.com>
Cc: Archana Muniganti <marchana@marvell.com>, <anoobj@marvell.com>,
	<dev@dpdk.org>
Subject: [PATCH 0/2] populate mbuf in latency test
Date: Fri, 8 Apr 2022 15:48:33 +0530	[thread overview]
Message-ID: <20220408101835.12941-1-marchana@marvell.com> (raw)

For decrypt, ICV mismatch can come as data is dummy and
latency will be calculated for error path. Hence populate
mbuf with test vector data.

Archana Muniganti (2):
  app/crypto-perf: populate mbuf in latency test
  app/crypto-perf: add vector file for AES-GCM

 app/test-crypto-perf/cperf_ops.c           |  3 +-
 app/test-crypto-perf/cperf_test_common.c   | 36 ++++++++
 app/test-crypto-perf/cperf_test_common.h   |  5 ++
 app/test-crypto-perf/cperf_test_latency.c  |  6 ++
 app/test-crypto-perf/cperf_test_verify.c   | 36 --------
 app/test-crypto-perf/data/aes_gcm_128.data | 97 ++++++++++++++++++++++
 6 files changed, 146 insertions(+), 37 deletions(-)
 create mode 100644 app/test-crypto-perf/data/aes_gcm_128.data

-- 
2.22.0


             reply	other threads:[~2022-04-08 10:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 10:18 Archana Muniganti [this message]
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

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=20220408101835.12941-1-marchana@marvell.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 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).