RE: [PATCH 1/3] security: introduce out of place support for inline ingress

2023-09-19 Thread Akhil Goyal
> Subject: [PATCH 1/3] security: introduce out of place support for inline > ingress > > Similar to out of place(OOP) processing support that exists for > Lookaside crypto/security sessions, Inline ingress security > sessions may also need out of place processing in usecase

[PATCH 1/3] security: introduce out of place support for inline ingress

2023-08-11 Thread Nithin Dabilpuram
Similar to out of place(OOP) processing support that exists for Lookaside crypto/security sessions, Inline ingress security sessions may also need out of place processing in usecases where original encrypted packet needs to be retained for post processing. So for NIC's which have such a kind of HW

RE: [PATCH 1/3] security: introduce out of place support for inline ingress

2023-05-31 Thread Morten Brørup
> From: Thomas Monjalon [mailto:tho...@monjalon.net] > Sent: Tuesday, 30 May 2023 15.52 > > 30/05/2023 11:23, Jerin Jacob: > > > > > > > + */ > > > > > > > + uint32_t ingress_oop : 1; > > > > > > > + > > > > > > > /** Reserved bit fields for future extension > > > > > > >* >

Re: [PATCH 1/3] security: introduce out of place support for inline ingress

2023-05-30 Thread Thomas Monjalon
30/05/2023 11:23, Jerin Jacob: > > > > > > + */ > > > > > > + uint32_t ingress_oop : 1; > > > > > > + > > > > > > /** Reserved bit fields for future extension > > > > > >* > > > > > >* User should ensure reserved_opts is cleared as it may > > > > > > change in > > >

Re: [PATCH 1/3] security: introduce out of place support for inline ingress

2023-05-30 Thread Jerin Jacob
> > > > > + */ > > > > > + uint32_t ingress_oop : 1; > > > > > + > > > > > /** Reserved bit fields for future extension > > > > >* > > > > >* User should ensure reserved_opts is cleared as it may change > > > > > in > > > > > @@ -282,7 +293,7 @@ struct rte_security_i

Re: [PATCH 1/3] security: introduce out of place support for inline ingress

2023-05-19 Thread Jerin Jacob
On Tue, Apr 25, 2023 at 4:11 AM Thomas Monjalon wrote: > > 18/04/2023 10:33, Jerin Jacob: > > On Tue, Apr 11, 2023 at 11:36 PM Stephen Hemminger > > wrote: > > > > > > On Tue, 11 Apr 2023 15:34:07 +0530 > > > Nithin Dabilpuram wrote: > > > > > > > diff --git a/lib/security/rte_security.h b/lib/s

Re: [PATCH 1/3] security: introduce out of place support for inline ingress

2023-04-24 Thread Thomas Monjalon
18/04/2023 10:33, Jerin Jacob: > On Tue, Apr 11, 2023 at 11:36 PM Stephen Hemminger > wrote: > > > > On Tue, 11 Apr 2023 15:34:07 +0530 > > Nithin Dabilpuram wrote: > > > > > diff --git a/lib/security/rte_security.h b/lib/security/rte_security.h > > > index 4bacf9fcd9..866cd4e8ee 100644 > > > ---

Re: [PATCH 1/3] security: introduce out of place support for inline ingress

2023-04-18 Thread Jerin Jacob
On Tue, Apr 11, 2023 at 11:36 PM Stephen Hemminger wrote: > > On Tue, 11 Apr 2023 15:34:07 +0530 > Nithin Dabilpuram wrote: > > > diff --git a/lib/security/rte_security.h b/lib/security/rte_security.h > > index 4bacf9fcd9..866cd4e8ee 100644 > > --- a/lib/security/rte_security.h > > +++ b/lib/secu

[PATCH 1/3] security: introduce out of place support for inline ingress

2023-04-11 Thread Nithin Dabilpuram
Similar to out of place(OOP) processing support that exists for Lookaside crypto/security sessions, Inline ingress security sessions may also need out of place processing in usecases where original encrypted packet needs to be retained for post processing. So for NIC's which have such a kind of HW