From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org
Cc: jerinj@marvell.com, abhinandan.gujjar@intel.com
Subject: [dpdk-dev] [PATCH 5/6] test/event_crypto: use device cap instead of fixed values
Date: Tue, 1 Oct 2019 17:03:38 +0530 [thread overview]
Message-ID: <20191001113339.21767-5-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <20191001113339.21767-1-hemant.agrawal@nxp.com>
Instead of hardcoded event device capabilities,
it is better to enquire and use the device supported caps.
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
app/test/test_event_crypto_adapter.c | 19 ++++++++-----------
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/app/test/test_event_crypto_adapter.c b/app/test/test_event_crypto_adapter.c
index b9e3a439e..6b10909e3 100644
--- a/app/test/test_event_crypto_adapter.c
+++ b/app/test/test_event_crypto_adapter.c
@@ -703,12 +703,11 @@ test_crypto_adapter_free(void)
static int
test_crypto_adapter_create(void)
{
- struct rte_event_port_conf conf = {
- .dequeue_depth = 8,
- .enqueue_depth = 8,
- .new_event_threshold = 1200,
- };
int ret;
+ struct rte_event_port_conf conf;
+
+ ret = rte_event_port_default_conf_get(TEST_CDEV_ID, 0, &conf);
+ TEST_ASSERT_SUCCESS(ret, "Failed to get port0 info");
/* Create adapter with default port creation callback */
ret = rte_event_crypto_adapter_create(TEST_ADAPTER_ID,
@@ -747,14 +746,12 @@ test_crypto_adapter_qp_add_del(void)
static int
configure_event_crypto_adapter(enum rte_event_crypto_adapter_mode mode)
{
- struct rte_event_port_conf conf = {
- .dequeue_depth = 8,
- .enqueue_depth = 8,
- .new_event_threshold = 1200,
- };
-
uint32_t cap;
int ret;
+ struct rte_event_port_conf conf;
+
+ ret = rte_event_port_default_conf_get(TEST_CDEV_ID, 0, &conf);
+ TEST_ASSERT_SUCCESS(ret, "Failed to get port0 info");
/* Create adapter with default port creation callback */
ret = rte_event_crypto_adapter_create(TEST_ADAPTER_ID,
--
2.17.1
next prev parent reply other threads:[~2019-10-01 11:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 11:33 [dpdk-dev] [PATCH 1/6] test/event_crypto: fix missing IV value for AES algo Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 2/6] test/event_crypto: fix check for HW support Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 3/6] test/event_crypto: fix to avail the mempool entries Hemant Agrawal
2019-10-01 11:33 ` [dpdk-dev] [PATCH 4/6] test/event_crypto: support to release the atomic ctxt Hemant Agrawal
2019-10-01 11:33 ` Hemant Agrawal [this message]
2019-10-01 11:33 ` [dpdk-dev] [PATCH 6/6] test/event_crypto: separate the NEW and FWD mode inits Hemant Agrawal
2019-10-03 3:24 ` [dpdk-dev] [PATCH 1/6] test/event_crypto: fix missing IV value for AES algo Jerin Jacob
2019-10-03 4:52 ` Gujjar, Abhinandan S
2019-10-04 9:35 ` Gujjar, Abhinandan S
2019-10-16 8:01 ` Jerin Jacob
2019-10-18 5:28 ` Hemant Agrawal
2019-11-07 9:01 ` [dpdk-dev] [PATCH v2 1/3] " Hemant Agrawal
2019-11-07 9:01 ` [dpdk-dev] [PATCH v2 2/3] test/event_crypto: fix to avail the mempool entries Hemant Agrawal
2019-11-07 9:01 ` [dpdk-dev] [PATCH v2 3/3] test/event_crypto: fix check for HW support Hemant Agrawal
2019-11-18 15:59 ` [dpdk-dev] [PATCH v2 1/3] test/event_crypto: fix missing IV value for AES algo Jerin Jacob
2019-11-18 16:02 ` Gujjar, Abhinandan S
2019-11-19 10:36 ` Gujjar, Abhinandan S
2019-11-20 13:39 ` Jerin Jacob
2019-11-26 5:55 ` 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=20191001113339.21767-5-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).