From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org, abhinandan.gujjar@intel.com
Cc: stable@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-dev] [PATCH] test/event_crypto: fix mempool name
Date: Fri, 27 Sep 2019 13:46:04 +0530 [thread overview]
Message-ID: <20190927081606.22931-1-hemant.agrawal@nxp.com> (raw)
The longer mempool name size is causing error in
rte_mempool_create_empty for dpaa1
ret = snprintf(mz_name, sizeof(mz_name), RTE_MEMPOOL_MZ_FORMAT, name);
This patch reduce the size of mempool name string
Fixes: 24054e3640a2 ("test/crypto: use separate session mempools")
Cc: stable@dpdk.org
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
app/test/test_event_crypto_adapter.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/test/test_event_crypto_adapter.c b/app/test/test_event_crypto_adapter.c
index 73655020d..cff7ad61f 100644
--- a/app/test/test_event_crypto_adapter.c
+++ b/app/test/test_event_crypto_adapter.c
@@ -536,7 +536,7 @@ configure_cryptodev(void)
"session mempool allocation failed\n");
params.session_priv_mpool = rte_mempool_create(
- "CRYPTO_ADAPTER_SESSION_MP_PRIV",
+ "CRYPTO_AD_SESS_MP_PRIV",
MAX_NB_SESSIONS,
session_size,
0, 0, NULL, NULL, NULL,
--
2.17.1
next reply other threads:[~2019-09-27 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 8:16 Hemant Agrawal [this message]
2019-09-27 8:16 ` [dpdk-dev] [PATCH] test/event_crypto: change the SEC cipher algo Hemant Agrawal
2019-09-27 10:11 ` Gujjar, Abhinandan S
2019-09-30 8:29 ` Jerin Jacob
2019-09-27 8:16 ` [dpdk-dev] [PATCH] test/event_crypto: add check for adapter failure Hemant Agrawal
2019-09-27 10:10 ` Gujjar, Abhinandan S
2019-09-30 13:27 ` Jerin Jacob
2019-09-27 10:09 ` [dpdk-dev] [PATCH] test/event_crypto: fix mempool name Gujjar, Abhinandan S
2019-09-30 8:18 ` Jerin Jacob
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=20190927081606.22931-1-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).