RE: [PATCH 1/2] security: introduce per session event metadata

Hi Abhinandan and others, > We may need to stick to the approach introduced in this patch only. > As if we propose, a new single API for all type of sessions, the driver would > need > to > Get the event metadata from the session private data. This is not possible > with > Your use case which get

RE: [PATCH 1/2] security: introduce per session event metadata

Hi Abhinandan and others, > + @Jayatheerthan, Jay & @Vangati, Narender > > > This change would be an ABI breakage. So to avoid that, we are planning to > > Propose a better solution compared to this patch. > > We plan to add a new cryptodev op to set the event metadata. A single API > > which can

RE: [PATCH 1/2] security: introduce per session event metadata

+ @Jayatheerthan, Jay & @Vangati, Narender > -Original Message- > From: Akhil Goyal > Sent: Monday, April 4, 2022 3:19 PM > To: Gujjar, Abhinandan S ; Volodymyr Fialko > ; dev@dpdk.org > Cc: Jerin Jacob Kollanukkaran ; Anoob Joseph > > Subject: RE: [PATCH

RE: [PATCH 1/2] security: introduce per session event metadata

Hi Abhinandan, > -- > Acked-by: Abhinandan Gujjar > This change would be an ABI breakage. So to avoid that, we are planning to Propose a better solution compared to this patch. We plan to add a new cryptodev op to set the event m

RE: [PATCH 1/2] security: introduce per session event metadata

Acked-by: Abhinandan Gujjar > -Original Message- > From: Volodymyr Fialko > Sent: Friday, March 25, 2022 4:46 PM > To: dev@dpdk.org; Gujjar, Abhinandan S ; Akhil > Goyal > Cc: jer...@marvell.com; Volodymyr Fialko ; Anoob > Joseph > Subject: [PATCH 1/2] security: introduce per session e