Hi Pablo,

> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Tuesday, February 13, 2018 8:27 PM
> To: Gujjar, Abhinandan S <[email protected]>; Doherty, Declan
> <[email protected]>; [email protected];
> [email protected]
> Cc: [email protected]; Vangati, Narender <[email protected]>; Rao,
> Nikhil <[email protected]>
> Subject: RE: [RFC v3, 2/3] cryptodev: add support to set session private data
> 
> Hi,
> 
> > -----Original Message-----
> > From: Gujjar, Abhinandan S
> > Sent: Thursday, February 1, 2018 9:30 AM
> > To: Doherty, Declan <[email protected]>; [email protected];
> > De Lara Guarch, Pablo <[email protected]>;
> > [email protected]
> > Cc: [email protected]; Vangati, Narender <[email protected]>;
> > Gujjar, Abhinandan S <[email protected]>; Rao, Nikhil
> > <[email protected]>
> > 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
> > rte_cryptodev_sym_session_get_private_data().
> >
> > Signed-off-by: Abhinandan Gujjar <[email protected]>
> > Signed-off-by: Nikhil Rao <[email protected]>
> 
> This looks good to me. I am expecting then a v1 with the implementation of
> these functions.
Sure. I will post the implementation.

Thanks
Abhinandan
> 
> Thanks,
> Pablo

Reply via email to