From: Akhil Goyal <gakhil@marvell.com>
To: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Ciara Power <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Subject: RE: [EXT] [PATCH] test/crypto-perf: extend asymmetric crypto throughput test
Date: Thu, 28 Apr 2022 10:22:25 +0000 [thread overview]
Message-ID: <CO6PR18MB44847128691DC701831CD135D8FD9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220316083412.1225979-1-kirankumark@marvell.com>
Hi Kiran,
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> Extended support for asymmetric crypto perf throughput test.
> Added support for new modulus lengths.
> Added new parameter --modex-len.
> Supported lengths are 60, 128, 255, 448. Default length is 128.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> ---
> app/test-crypto-perf/cperf_ops.c | 18 +-
> app/test-crypto-perf/cperf_options.h | 3 +
> app/test-crypto-perf/cperf_options_parsing.c | 42 +++
> app/test-crypto-perf/cperf_test_vectors.c | 264 ++++++++++++++++---
> app/test-crypto-perf/cperf_test_vectors.h | 25 +-
> app/test-crypto-perf/main.c | 2 +-
> 6 files changed, 307 insertions(+), 47 deletions(-)
Can you also add the new param in doc/guides/tools/cryptoperf.rst
Other than that
Acked-by: Akhil Goyal <gakhil@marvell.com>
next prev parent reply other threads:[~2022-04-28 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 8:34 kirankumark
2022-04-28 10:22 ` Akhil Goyal [this message]
2022-04-29 6:23 ` [dpdk-dev][PATCH] " kirankumark
2022-04-29 6:54 ` [EXT] " Akhil Goyal
2022-04-29 9:05 ` 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=CO6PR18MB44847128691DC701831CD135D8FD9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kirankumark@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).