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
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
the proposal soon. Would need your help in testing the Intel
> usecases.
>
> Regards,
> Akhil
> > > -Original Message-
> > > From: Volodymyr Fialko
> > > Sent: Friday, March 25, 2022 4:46 PM
> > > To: dev@dpdk.org; Gujjar, Abhinandan S
> > > ;
>
t; > 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 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] securit
Implement API to set/get event data per security session.
Signed-off-by: Volodymyr Fialko
Acked-by: Akhil Goyal
Acked-by: Anoob Joseph
---
.../prog_guide/event_crypto_adapter.rst | 4 +-
lib/security/rte_security.h | 43 +++
2 files changed, 45 insertio
6 matches
Mail list logo
