From: Kai Ji <kai.ji@intel.com>
To: dev@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>, pablo.de.lara.guarch@intel.com
Subject: [dpdk-dev] [dpdk-dev v2] test/crypto-perf: fix crypto perf out-of-place mempool alloc
Date: Mon, 24 May 2021 17:46:27 +0100 [thread overview]
Message-ID: <20210524164627.15204-1-kai.ji@intel.com> (raw)
In-Reply-To: <20210520150711.28196-1-kai.ji@intel.com>
Add in missing rte_mbuf size in mempool allocation for out-of-place op.
Fixes: bf9d6702eca9 ("app/crypto-perf: use single mempool")
Cc: pablo.de.lara.guarch@intel.com
Signed-off-by: Kai Ji <kai.ji@intel.com>
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
v2:
-- commit message update
app/test-crypto-perf/cperf_test_common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test-crypto-perf/cperf_test_common.c b/app/test-crypto-perf/cperf_test_common.c
index 058e0ba564..12925c7f22 100644
--- a/app/test-crypto-perf/cperf_test_common.c
+++ b/app/test-crypto-perf/cperf_test_common.c
@@ -194,7 +194,7 @@ cperf_alloc_common_memory(const struct cperf_options *options,
(mbuf_size * segments_nb);
params.dst_buf_offset = *dst_buf_offset;
/* Destination buffer will be one segment only */
- obj_size += max_size;
+ obj_size += max_size + sizeof(struct rte_mbuf);
}
*pool = rte_mempool_create_empty(pool_name,
--
2.17.1
next prev parent reply other threads:[~2021-05-24 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 15:07 [dpdk-dev] [dpdk-dev v1] cperf: " Kai Ji
2021-05-21 9:04 ` Zhang, Roy Fan
2021-05-21 11:18 ` De Lara Guarch, Pablo
2021-05-21 15:36 ` Thomas Monjalon
2021-05-24 7:23 ` Zhang, Roy Fan
2021-05-24 16:46 ` Kai Ji [this message]
2021-06-29 20:11 ` [dpdk-dev] [EXT] [dpdk-dev v2] test/crypto-perf: " 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=20210524164627.15204-1-kai.ji@intel.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.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).