From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org
Cc: jerinj@marvell.com, abhinandan.gujjar@intel.com
Subject: [dpdk-dev] [PATCH 4/6] test/event_crypto: support to release the atomic ctxt
Date: Tue, 1 Oct 2019 17:03:37 +0530 [thread overview]
Message-ID: <20191001113339.21767-4-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <20191001113339.21767-1-hemant.agrawal@nxp.com>
The test cases uses ATOMIC queues. Once the packet is recived
it is required to release the ATOMIC ctxt, at least for the
HW based eventdevs. This patch makes empty dq call, which
in turn releases the atomic ctxt.
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
app/test/test_event_crypto_adapter.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/app/test/test_event_crypto_adapter.c b/app/test/test_event_crypto_adapter.c
index 8d42462d8..b9e3a439e 100644
--- a/app/test/test_event_crypto_adapter.c
+++ b/app/test/test_event_crypto_adapter.c
@@ -357,6 +357,12 @@ send_op_recv_ev(struct rte_crypto_op *op)
rte_pause();
recv_op = ev.event_ptr;
+
+ /* In case of Atomic/Ordered Queue, call dequeue one more time
+ * to release, if there is any atomic context to be freed
+ */
+ rte_event_dequeue_burst(evdev, TEST_APP_PORT_ID, &ev, NUM, 0);
+
#if PKT_TRACE
struct rte_mbuf *m = recv_op->sym->m_src;
rte_pktmbuf_dump(stdout, m, rte_pktmbuf_pkt_len(m));
--
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 ` Hemant Agrawal [this message]
2019-10-01 11:33 ` [dpdk-dev] [PATCH 5/6] test/event_crypto: use device cap instead of fixed values Hemant Agrawal
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-4-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).