> -----Original Message-----
> From: Gujjar, Abhinandan S
> Sent: Thursday, February 1, 2018 9:30 AM
> To: Doherty, Declan <declan.dohe...@intel.com>; akhil.go...@nxp.com; De
> Lara Guarch, Pablo <pablo.de.lara.gua...@intel.com>;
> Cc: firstname.lastname@example.org; Vangati, Narender <narender.vang...@intel.com>;
> Gujjar, Abhinandan S <abhinandan.guj...@intel.com>; Rao, Nikhil
> Subject: [RFC v3, 2/3] cryptodev: add support to set session private data
> The application may want to store private data along with the
> rte_cryptodev that is transparent to the rte_cryptodev layer.
> For e.g., If an eventdev based application is submitting a
> rte_cryptodev_sym_session operation and wants to indicate event
> information required to construct a new event that will be enqueued to
> eventdev after completion of the rte_cryptodev_sym_session operation.
> This patch provides a mechanism for the application to associate this
> information with the rte_cryptodev_sym_session session.
> The application can set the private data using
> rte_cryptodev_sym_session_set_private_data() and retrieve it using
> Signed-off-by: Abhinandan Gujjar <abhinandan.guj...@intel.com>
> Signed-off-by: Nikhil Rao <nikhil....@intel.com>
This looks good to me. I am expecting then a v1 with the implementation of