On 8/19/2019 8:09 AM, Akhil Goyal wrote:
> Hi Anoob,
>>
>> Hi Akhil,
>>
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 hardwar
Hi Anoob,
>
> Hi Akhil,
>
> > > > > > >
> > > > > > > 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 wo
ob Kollanukkaran ; Narayana Prasad Raju
> Athreya ; Ankur Dwivedi
> ; Shahaf Shuler ;
> Hemant Agrawal ; Matan Azrad
> ; Yongseok Koh ; Wenzhuo
> Lu ; Konstantin Ananyev
> ; Radu Nicolau ;
> dev@dpdk.org
> Subject: Re: [dpdk-dev] [RFC] ethdev: allow multiple security sessions to
Hi Anoob,
>
> Hi Akhil,
>
> > > > >
> > > > > 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
> > > > cl
Hi Konstantin,
Please see inline.
Thanks,
Anoob
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Thursday, August 15, 2019 3:18 PM
> To: Anoob Joseph ; Akhil Goyal
> ; Adrien Mazarguil ;
> Doherty, Declan ; De Lara Guarch, Pablo
> ; Thomas Monjalon
>
> Cc: Jerin Jacob Kollanukk
Hi Anoob,
>
> > > > >
> > > > > 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 Akhil,
Please see inline.
Thanks,
Anoob
> -Original Message-
> From: Akhil Goyal
> Sent: Wednesday, August 14, 2019 4:37 PM
> To: Anoob Joseph ; Adrien Mazarguil
> ; Declan Doherty
> ; Pablo de Lara
> ; Thomas Monjalon
>
> Cc: Jerin Jacob Kollanukkaran ; Narayana Prasad Raju
> Athre
Hi Anoob,
>
> Hi all,
>
> Reminder...!
>
Sorry for a delayed response.
> If there are no concerns, I'll send the patch after adding the required
> changes in
> ipsec-secgw as well.
>
> Thanks,
> Anoob
>
> > -Original Message-
> > From: Anoob Joseph
> > Sent: Friday, August 2, 2019
Hi all,
Reminder...!
If there are no concerns, I'll send the patch after adding the required changes
in ipsec-secgw as well.
Thanks,
Anoob
> -Original Message-
> From: Anoob Joseph
> Sent: Friday, August 2, 2019 11:05 AM
> To: Anoob Joseph ; Akhil Goyal
> ; Adrien Mazarguil ;
> Declan
Hi Akhil, Adrien, Declan, Pablo,
Can you review this proposal and share your feedback?
Thanks,
Anoob
> -Original Message-
> From: Anoob Joseph
> Sent: Wednesday, July 24, 2019 7:47 PM
> To: Akhil Goyal ; Adrien Mazarguil
> ; Declan Doherty
> ; Pablo de Lara
> ; 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. And if an rte_flo
11 matches
Mail list logo
