10/12/2019 21:47, Ori Kam:
>
> > -Original Message-
> > Subject: Re: [dpdk-dev] [PATCH] ethdev: allow multiple security sessions to
> > use one rte flow
> >
> > On Sun, Dec 8, 2019 at 4:19 PM Anoob Joseph wrote:
> > >
> > > The rt
, Ferruh ; Jerin Jacob
Kollanukkaran ; Thomas Monjalon
Cc: Ankur Dwivedi ; Hemant Agrawal
; Matan Azrad ; Nicolau,
Radu ; Shahaf Shuler ;
Narayana Prasad Raju Athreya ; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: allow multiple security sessions to use
one rte flow
The rte_security API
Hi Konstantin,
Please see inline.
Thanks,
Anoob
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Monday, December 16, 2019 6:24 PM
> To: Anoob Joseph ; Akhil Goyal ;
> Adrien Mazarguil ; Doherty, Declan
> ; Yigit, Ferruh ; Jerin
> Jacob
> Kollanukkaran ; Thomas Monjalon
>
> Cc
> > > > > > > The rte_security API which enables inline protocol/crypto
> > > > > > > feature mandates that for every security session an rte_flow is
> > > > > > > created.
> > > > > > > This would internally translate to a rule in the hardware
> > > > > > > which would do packet classification.
Hi Konstantin,
Please see inline.
Thanks,
Anoob
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Friday, December 13, 2019 5:25 PM
> To: Anoob Joseph ; Akhil Goyal ;
> Adrien Mazarguil ; Doherty, Declan
> ; Yigit, Ferruh ; Jerin
> Jacob
> Kollanukkaran ; Thomas Monjalon
>
> Cc
> > > > > The rte_security API which enables inline protocol/crypto feature
> > > > > mandates that for every security session an rte_flow is created.
> > > > > This would internally translate to a rule in the hardware which
> > > > > would do packet classification.
> > > > >
> > > > > In rte_secur
Jacob
> Kollanukkaran ; Thomas Monjalon
>
> Cc: Ankur Dwivedi ; Hemant Agrawal
> ; Matan Azrad ; Nicolau,
> Radu ; Shahaf Shuler ;
> Narayana Prasad Raju Athreya ; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] ethdev: allow multiple security sessions to
> use
> one rte flow
> > >
> > > The rte_security API which enables inline protocol/crypto feature
> > > mandates that for every security session an rte_flow is created. This
> > > would internally translate to a rule in the hardware which would do
> > > packet classification.
> > >
> > > In rte_securty, one SA would
> -Original Message-
> Subject: Re: [dpdk-dev] [PATCH] ethdev: allow multiple security sessions to
> use one rte flow
>
> On Sun, Dec 8, 2019 at 4:19 PM Anoob Joseph wrote:
> >
> > The rte_security API which enables inline protocol/crypto feature
> >
Hi Konstantin,
Please see inline.
Thanks,
Anoob
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Monday, December 9, 2019 6:49 PM
> To: Anoob Joseph ; Akhil Goyal ;
> Adrien Mazarguil ; Doherty, Declan
> ; Yigit, Ferruh ; Jerin
> Jacob
> Kollanukkaran ; Thomas Monjalon
>
> Cc:
>
> The rte_security API which enables inline protocol/crypto feature
> mandates that for every security session an rte_flow is created. This
> would internally translate to a rule in the hardware which would do
> packet classification.
>
> In rte_securty, one SA would be one security session.
On Sun, Dec 8, 2019 at 4:19 PM Anoob Joseph wrote:
>
> The rte_security API which enables inline protocol/crypto feature
> mandates that for every security session an rte_flow is created. This
> would internally translate to a rule in the hardware which would do
> packet classification.
>
> In rte
The rte_security API which enables inline protocol/crypto feature
mandates that for every security session an rte_flow is created. This
would internally translate to a rule in the hardware which would do
packet classification.
In rte_securty, one SA would be one security session. And if an rte_flo
13 matches
Mail list logo
