From: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
To: jerin.jacob@caviumnetworks.com, thomas@monjalon.net, dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, abhinandan.gujjar@intel.com
Subject: [dpdk-dev] [PATCH] test: fix build with icc
Date: Mon, 14 May 2018 12:20:22 +0530 [thread overview]
Message-ID: <1526280622-50931-1-git-send-email-abhinandan.gujjar@intel.com> (raw)
This patch provides fix for icc compilation issue with event
crypto adapter test application.
Currently, number of elements in the session mempool is defined
by max_nb_sessions & this is replaced with a macro.
Fixes: 3c2c535ecfc0 ("test: add event crypto adapter auto-test")
Reported-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
---
test/test/test_event_crypto_adapter.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/test/test/test_event_crypto_adapter.c b/test/test/test_event_crypto_adapter.c
index 17eae5d..6f0e794 100644
--- a/test/test/test_event_crypto_adapter.c
+++ b/test/test/test_event_crypto_adapter.c
@@ -21,6 +21,7 @@
#define MBUF_CACHE_SIZE (256)
#define MAXIMUM_IV_LENGTH (16)
#define DEFAULT_NUM_OPS_INFLIGHT (128)
+#define MAX_NB_SESSIONS 4
#define TEST_APP_PORT_ID 0
#define TEST_APP_EV_QUEUE_ID 0
#define TEST_APP_EV_PRIORITY 0
@@ -527,7 +528,7 @@ struct rte_event_crypto_request request_info = {
params.session_mpool = rte_mempool_create(
"CRYPTO_ADAPTER_SESSION_MP",
- info.sym.max_nb_sessions * 2,
+ MAX_NB_SESSIONS * 2,
session_size,
0, 0, NULL, NULL, NULL,
NULL, SOCKET_ID_ANY,
--
1.9.1
next reply other threads:[~2018-05-14 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 6:50 Abhinandan Gujjar [this message]
2018-05-14 8:13 ` De Lara Guarch, Pablo
2018-05-14 9:21 ` Thomas Monjalon
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=1526280622-50931-1-git-send-email-abhinandan.gujjar@intel.com \
--to=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pablo.de.lara.guarch@intel.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).