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>,
Gage Eads <gage.eads@intel.com>,
"Athreya, Narayana Prasad" <NarayanaPrasad.Athreya@cavium.com>,
"Murthy, Nidadavolu" <Nidadavolu.Murthy@cavium.com>
Subject: Re: [dpdk-dev] [dpdk-dev, v1, 2/5] eventdev: add crypto adapter implementation
Date: Fri, 20 Apr 2018 12:48:20 +0000 [thread overview]
Message-ID: <CY4PR0701MB3634C002759E7207112F030EF0B40@CY4PR0701MB3634.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1522824999-61614-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; Gage Eads <gage.eads@intel.com>
>Subject: [dpdk-dev] [dpdk-dev, v1, 2/5] eventdev: add crypto adapter implementation
>
>Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
>Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
>Signed-off-by: Gage Eads <gage.eads@intel.com>
>---
> config/common_base | 1 +
> lib/Makefile | 3 +-
> lib/librte_eventdev/Makefile | 3 +
> lib/librte_eventdev/rte_event_crypto_adapter.c | 1089 ++++++++++++++++++++++++
> lib/librte_eventdev/rte_event_crypto_adapter.h | 449 ++++++++++
> lib/librte_eventdev/rte_eventdev_version.map | 12 +
> 6 files changed, 1556 insertions(+), 1 deletion(-)
> create mode 100644 lib/librte_eventdev/rte_event_crypto_adapter.c
> create mode 100644 lib/librte_eventdev/rte_event_crypto_adapter.h
>
//snip
>diff --git a/lib/librte_eventdev/rte_event_crypto_adapter.h b/lib/librte_eventdev/rte_event_crypto_adapter.h
>new file mode 100644
>index 0000000..a974464
>--- /dev/null
>+++ b/lib/librte_eventdev/rte_event_crypto_adapter.h
>@@ -0,0 +1,449 @@
//snip
>+/**
>+ * @warning
>+ * @b EXPERIMENTAL: this API may change without prior notice
>+ *
>+ * Create a new event crypto adapter with the specified identifier.
>+ * This function uses an internal configuration function that creates an event
>+ * port. This default function reconfigures the event device with an
>+ * additional event port and setups up the event port using the port_config
>+ * parameter passed into this function. In case the application needs more
>+ * control in configuration of the service, it should use the
>+ * rte_event_crypto_adapter_create_ext() version.
>+ *
>+ * @param id
>+ * Adapter identifier.
>+ *
>+ * @param cdev_id
>+ * Crypto device identifier.
[Shally] As I understood, API create crypto adapter on an event device. Is that correct? If yes, so, should it be crypto dev id or event device id?
Thanks
Shally
>+ *
>+ * @param port_config
>+ * Argument of type *rte_event_port_conf* that is passed to the conf_cb
>+ * function.
>+ *
>+ * @return
>+ * - 0: Success
>+ * - <0: Error code on failure
>+ */
>+int __rte_experimental
>+rte_event_crypto_adapter_create(uint8_t id, uint8_t cdev_id,
>+ struct rte_event_port_conf *port_config);
>+
//snip
next prev parent reply other threads:[~2018-04-20 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 6:56 Abhinandan Gujjar
2018-04-17 14:18 ` Akhil Goyal
2018-04-18 6:21 ` Gujjar, Abhinandan S
2018-04-20 11:34 ` Akhil Goyal
2018-04-20 12:09 ` Gujjar, Abhinandan S
2018-04-20 13:14 ` Jerin Jacob
2018-04-23 6:39 ` Akhil Goyal
2018-04-23 6:49 ` Gujjar, Abhinandan S
2018-04-20 12:48 ` Verma, Shally [this message]
2018-04-20 15:18 ` 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=CY4PR0701MB3634C002759E7207112F030EF0B40@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=gage.eads@intel.com \
--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).