From: Akhil Goyal <gakhil@marvell.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
Suanming Mou <suanmingm@nvidia.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Ji, Kai" <kai.ji@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2] app/test-crypto-perf: add throughput OOP decryption
Date: Fri, 19 Jul 2024 15:43:47 +0000 [thread overview]
Message-ID: <CO6PR18MB4484356910B90AE31A5D2202D8AD2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR11MB5056BFADD87AC88A14A090F483AD2@SJ0PR11MB5056.namprd11.prod.outlook.com>
> > > > > Subject: [PATCH v2] app/test-crypto-perf: add throughput OOP
> > > > > decryption
> > > > >
> > > > > During throughput running, re-filling the test data will impact
> > > > > the performance test result. So for now, to run decrypt throughput
> > > > > testing is not supported
> > > since
> > > > > the test data is not filled.
> > > > >
> > > > > But if user requires OOP(out-of-place) mode, the test data from
> > > > > source mbuf
> > > > will
> > > > > never be modified, and if the test data can be prepared out of the
> > > > > running
> > > loop,
> > > > > the decryption test should be fine.
> > > > >
> > > > > This commit adds the support of out-of-place decryption testing
> > > > > for
> > > throughput.
> > > > >
> > > > > Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> > > > > ---
> > > > > app/test-crypto-perf/cperf_ops.c | 5 ++-
> > > > > app/test-crypto-perf/cperf_options_parsing.c | 8 +++++
> > > > > app/test-crypto- perf/cperf_test_throughput.c | 34
> > > > > +++++++++++++++++---
> > > > > 3 files changed, 41 insertions(+), 6 deletions(-)
> > > > >
> Acked-by: Brian Dooley <brian.dooley@intel.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2024-07-19 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 10:01 [PATCH] " Suanming Mou
2024-03-14 18:44 ` [EXT] " Akhil Goyal
2024-03-19 1:57 ` Suanming Mou
2024-03-19 8:23 ` Akhil Goyal
2024-03-19 9:06 ` Suanming Mou
2024-03-19 9:32 ` Akhil Goyal
2024-03-19 11:43 ` Suanming Mou
2024-03-19 11:46 ` [PATCH v2] " Suanming Mou
2024-03-19 15:14 ` Power, Ciara
2024-03-20 0:14 ` Suanming Mou
2024-04-01 0:30 ` Suanming Mou
2024-06-14 9:38 ` Suanming Mou
2024-06-20 6:44 ` Akhil Goyal
2024-07-18 19:57 ` Akhil Goyal
2024-07-19 15:13 ` Dooley, Brian
2024-07-19 15:43 ` 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=CO6PR18MB4484356910B90AE31A5D2202D8AD2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=kai.ji@intel.com \
--cc=suanmingm@nvidia.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).