From: Tejasree Kondoj <ktejasree@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <royzhang1980@gmail.com>,
Ciara Power <ciara.power@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>, <dev@dpdk.org>
Subject: [PATCH] app/crypto-perf: change buffer size based on optype
Date: Thu, 6 Apr 2023 13:46:20 +0530 [thread overview]
Message-ID: <20230406081620.497772-1-ktejasree@marvell.com> (raw)
Adding digest size to buffer size in auth-then-cipher
mode with auth_op set to generate as cipher length
includes digest size also.
Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
---
app/test-crypto-perf/cperf_options_parsing.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/app/test-crypto-perf/cperf_options_parsing.c b/app/test-crypto-perf/cperf_options_parsing.c
index 8c9f632590..849a5d6bb4 100644
--- a/app/test-crypto-perf/cperf_options_parsing.c
+++ b/app/test-crypto-perf/cperf_options_parsing.c
@@ -1064,6 +1064,10 @@ check_cipher_buffer_length(struct cperf_options *options)
else
buffer_size = options->buffer_size_list[0];
+ if ((options->auth_op == RTE_CRYPTO_AUTH_OP_GENERATE) &&
+ (options->op_type == CPERF_AUTH_THEN_CIPHER))
+ buffer_size += options->digest_sz;
+
while (buffer_size <= options->max_buffer_size) {
if ((buffer_size % AES_BLOCK_SIZE) != 0) {
RTE_LOG(ERR, USER1, "Some of the buffer sizes are "
@@ -1090,6 +1094,10 @@ check_cipher_buffer_length(struct cperf_options *options)
else
buffer_size = options->buffer_size_list[0];
+ if ((options->auth_op == RTE_CRYPTO_AUTH_OP_GENERATE) &&
+ (options->op_type == CPERF_AUTH_THEN_CIPHER))
+ buffer_size += options->digest_sz;
+
while (buffer_size <= options->max_buffer_size) {
if ((buffer_size % DES_BLOCK_SIZE) != 0) {
RTE_LOG(ERR, USER1, "Some of the buffer sizes are "
--
2.25.1
next reply other threads:[~2023-04-06 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 8:16 Tejasree Kondoj [this message]
2023-04-07 10:19 ` Power, Ciara
2023-04-10 3:10 ` Anoob Joseph
2023-05-24 9:29 ` 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=20230406081620.497772-1-ktejasree@marvell.com \
--to=ktejasree@marvell.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=royzhang1980@gmail.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).