[dpdk-dev] [dpdk-dev, v1, 2/5] eventdev: add crypto adapter implementation

Gujjar, Abhinandan S abhinandan.gujjar at intel.com
Fri Apr 20 17:18:14 CEST 2018



> -----Original Message-----
> From: Verma, Shally [mailto:Shally.Verma at cavium.com]
> Sent: Friday, April 20, 2018 6:18 PM
> To: Gujjar, Abhinandan S <abhinandan.gujjar at intel.com>; Jacob, Jerin
> <Jerin.JacobKollanukkaran at cavium.com>; hemant.agrawal at nxp.com;
> akhil.goyal at nxp.com; dev at dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch at intel.com>; Doherty, Declan
> <declan.doherty at intel.com>; Vangati, Narender
> <narender.vangati at intel.com>; Rao, Nikhil <nikhil.rao at intel.com>; Eads, Gage
> <gage.eads at intel.com>; Athreya, Narayana Prasad
> <NarayanaPrasad.Athreya at cavium.com>; Murthy, Nidadavolu
> <Nidadavolu.Murthy at cavium.com>
> Subject: RE: [dpdk-dev] [dpdk-dev, v1, 2/5] eventdev: add crypto adapter
> implementation
> 
> HI,
> 
> >-----Original Message-----
> >From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Abhinandan Gujjar
> >Sent: 04 April 2018 12:27
> >To: Jacob, Jerin <Jerin.JacobKollanukkaran at cavium.com>;
> >hemant.agrawal at nxp.com; akhil.goyal at nxp.com; dev at dpdk.org
> >Cc: pablo.de.lara.guarch at intel.com; declan.doherty at intel.com;
> >narender.vangati at intel.com; abhinandan.gujjar at intel.com;
> >nikhil.rao at intel.com; Gage Eads <gage.eads at intel.com>
> >Subject: [dpdk-dev] [dpdk-dev, v1, 2/5] eventdev: add crypto adapter
> >implementation
> >
> >Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar at intel.com>
> >Signed-off-by: Nikhil Rao <nikhil.rao at intel.com>
> >Signed-off-by: Gage Eads <gage.eads at 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?
[Abhinandan] You are right. The implementation actually uses this variable as eventdev id.
I will fix this in v2.
> 
> 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



More information about the dev mailing list