From: "Verma, Shally" <Shally.Verma@cavium.com>
To: Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
"Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"narender.vangati@intel.com" <narender.vangati@intel.com>,
"nikhil.rao@intel.com" <nikhil.rao@intel.com>,
"Athreya, Narayana Prasad" <NarayanaPrasad.Athreya@cavium.com>,
"Murthy, Nidadavolu" <Nidadavolu.Murthy@cavium.com>
Subject: Re: [dpdk-dev] [dpdk-dev, v1, 3/5] test: add event crypto adapter auto-test
Date: Fri, 20 Apr 2018 13:00:46 +0000 [thread overview]
Message-ID: <CY4PR0701MB3634AD12DA3A5FD806E5111BF0B40@CY4PR0701MB3634.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1522825021-61657-1-git-send-email-abhinandan.gujjar@intel.com>
HI
>-----Original Message-----
>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Abhinandan Gujjar
>Sent: 04 April 2018 12:27
>To: Jacob, Jerin <Jerin.JacobKollanukkaran@cavium.com>; hemant.agrawal@nxp.com; akhil.goyal@nxp.com; dev@dpdk.org
>Cc: pablo.de.lara.guarch@intel.com; declan.doherty@intel.com; narender.vangati@intel.com; abhinandan.gujjar@intel.com;
>nikhil.rao@intel.com
>Subject: [dpdk-dev] [dpdk-dev, v1, 3/5] test: add event crypto adapter auto-test
>
>Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
//snip
>+++ b/test/test/test_event_crypto_adapter.c
>@@ -0,0 +1,866 @@
>+/* SPDX-License-Identifier: BSD-3-Clause
>+ * Copyright(c) 2018 Intel Corporation
>+ */
>+
//snip
>+static int
>+send_recv_ev(struct rte_event *ev)
>+{
>+ struct rte_crypto_op *op;
>+ struct rte_event recv_ev;
>+ int ret;
>+
>+
>+ ret = rte_event_enqueue_burst(evdev, TEST_PORT_ID, ev, 1);
[Shally] Shouldn't it enqueue to a port id returned by rte_event_crypto_adapter_event_port_get () as adapter will dequeue from that port from eventdev?
>+ TEST_ASSERT_EQUAL(ret, 1, "Failed to send event to crypto adapter\n");
>+
>+ while (rte_event_dequeue_burst(evdev,
>+ TEST_PORT_ID, &recv_ev, 1, 0) == 0)
>+ rte_pause();
>+
>+ op = recv_ev.event_ptr;
>+#if PKT_TRACE
>+ struct rte_mbuf *m = op->sym->m_src;
>+ rte_pktmbuf_dump(stdout, m, rte_pktmbuf_pkt_len(m));
>+#endif
>+ rte_pktmbuf_free(op->sym->m_src);
>+ rte_crypto_op_free(op);
>+
>+ return TEST_SUCCESS;
>+}
//snip
--
>1.9.1
Thanks
Shally
next prev parent reply other threads:[~2018-04-20 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 6:57 Abhinandan Gujjar
2018-04-20 13:00 ` Verma, Shally [this message]
2018-04-20 15:31 ` Gujjar, Abhinandan S
2018-04-23 5:13 ` Verma, Shally
2018-04-23 5:42 ` Gujjar, Abhinandan S
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=CY4PR0701MB3634AD12DA3A5FD806E5111BF0B40@CY4PR0701MB3634.namprd07.prod.outlook.com \
--to=shally.verma@cavium.com \
--cc=Jerin.JacobKollanukkaran@cavium.com \
--cc=NarayanaPrasad.Athreya@cavium.com \
--cc=Nidadavolu.Murthy@cavium.com \
--cc=abhinandan.gujjar@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=narender.vangati@intel.com \
--cc=nikhil.rao@intel.com \
--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).