From: Akhil Goyal <gakhil@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Sachin Saxena <sachin.saxena@oss.nxp.com>,
Ciara Power <ciara.power@intel.com>
Cc: Aakash Sasidharan <asasidharan@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 0/1] Add security perf application
Date: Thu, 18 Aug 2022 09:31:41 +0000 [thread overview]
Message-ID: <PH0PR18MB4491B00C5C1FF01062E92AF8D86D9@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220811035933.802-1-anoobj@marvell.com>
Hi Anoob,
> Subject: [PATCH 0/1] Add security perf application
>
> Add performance application to test security session create & destroy
> rates supported by the security enabled cryptodev PMD. The
> application would create specified number of sessions and captures the
> time taken for the same before proceeding to destroy of the same. When
> operating on multi-core, the number of sessions would be evenly
> distributed across all cores.
>
> The application would test with all combinations of cipher & auth
> algorithms supported by the PMD.
>
> The app is similar to 'test-flow-perf' tool which captures the rate
> at which flow rules can be created and destroyed.
>
Is it not good to add this into dpdk-test-crypto-perf?
Can we add as a separate .c file, say, cperf_test_sec_session.c
in test-crypto-perf folder and use the existing framework.
This way we can leverage it for crypto sessions also.
> Anoob Joseph (1):
> app/test-security-perf: add security perf app
>
> MAINTAINERS | 6 +
> app/meson.build | 1 +
> app/test-security-perf/meson.build | 14 +
> app/test-security-perf/test_security_perf.c | 554 ++++++++++++++++++++
> doc/guides/tools/index.rst | 1 +
> doc/guides/tools/securityperf.rst | 47 ++
> 6 files changed, 623 insertions(+)
> create mode 100644 app/test-security-perf/meson.build
> create mode 100644 app/test-security-perf/test_security_perf.c
> create mode 100644 doc/guides/tools/securityperf.rst
>
> --
> 2.25.1
next prev parent reply other threads:[~2022-08-18 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 3:59 Anoob Joseph
2022-08-11 3:59 ` [PATCH 1/1] app/test-security-perf: add security perf app Anoob Joseph
2022-08-18 9:31 ` Akhil Goyal [this message]
2022-08-19 7:20 ` [PATCH 0/1] Add security perf application Anoob Joseph
2022-09-26 9:25 ` Anoob Joseph
2022-09-27 19:16 ` Akhil Goyal
2022-09-28 7:39 ` Anoob Joseph
2022-10-21 15:13 ` Akhil Goyal
2022-10-21 16:38 ` [PATCH v2] app/test-security-perf: add security perf app Anoob Joseph
2022-11-02 11:17 ` [PATCH v3] " Anoob Joseph
2022-11-03 12:46 ` [PATCH v4] " Anoob Joseph
2022-11-03 12:58 ` 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=PH0PR18MB4491B00C5C1FF01062E92AF8D86D9@PH0PR18MB4491.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=asasidharan@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=thomas@monjalon.net \
/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).