HI, >-----Original Message----- >From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Abhinandan Gujjar >Sent: 04 April 2018 12:27 >To: Jacob, Jerin <jerin.jacobkollanukka...@cavium.com>; >hemant.agra...@nxp.com; akhil.go...@nxp.com; dev@dpdk.org >Cc: pablo.de.lara.gua...@intel.com; declan.dohe...@intel.com; >narender.vang...@intel.com; abhinandan.guj...@intel.com; >nikhil....@intel.com; Gage Eads <gage.e...@intel.com> >Subject: [dpdk-dev] [dpdk-dev, v1, 2/5] eventdev: add crypto adapter >implementation > >Signed-off-by: Abhinandan Gujjar <abhinandan.guj...@intel.com> >Signed-off-by: Nikhil Rao <nikhil....@intel.com> >Signed-off-by: Gage Eads <gage.e...@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
