> > > > > > > >
> > > > > > > > 11/10/2019 14:40, Akhil Goyal:
> > > > > > > > > Hi All,
> > > > > > > > >
> > > > > > > > > This patchset would need ack from more vendors as it will
> > > > > > > > > impact user
> > > > > > > > experience
> > > > > > > > > on a key example application which is
Hi Akhil, Konstantin,
Please see inline.
Thanks,
Anoob
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Monday, November 4, 2019 8:55 PM
> To: Akhil Goyal ; Iremonger, Bernard
> ; Thomas Monjalon
> Cc: dev@dpdk.org; Anoob Joseph ; Jerin Jacob
> Kollanukkaran ; dpdk-techboard
>
Hi Akhil,
> >
> > > > > > > >
> > > > > > > > 11/10/2019 14:40, Akhil Goyal:
> > > > > > > > > Hi All,
> > > > > > > > >
> > > > > > > > > This patchset would need ack from more vendors as it will
> > > > > > > > > impact
> > > > > > > > > user
> > > > > > > > experience
> > > > > > > > > on a k
Hi Konstantin,
>
> Hi Akhil,
>
> > > > > > >
> > > > > > > 11/10/2019 14:40, Akhil Goyal:
> > > > > > > > Hi All,
> > > > > > > >
> > > > > > > > This patchset would need ack from more vendors as it will impact
> > > > > > > > user
> > > > > > > experience
> > > > > > > > on a key example appl
Hi Akhil,
> > > > > >
> > > > > > 11/10/2019 14:40, Akhil Goyal:
> > > > > > > Hi All,
> > > > > > >
> > > > > > > This patchset would need ack from more vendors as it will impact
> > > > > > > user
> > > > > > experience
> > > > > > > on a key example application which is normally demonstrated to
Hi Bernard,
>
> Hi Akhil,
>
> >
> >
> > > > >
> > > > > 11/10/2019 14:40, Akhil Goyal:
> > > > > > Hi All,
> > > > > >
> > > > > > This patchset would need ack from more vendors as it will impact
> > > > > > user
> > > > > experience
> > > > > > on a key example application which is normally demo
Hi Akhil,
> -Original Message-
> From: Akhil Goyal
> Sent: Tuesday, October 15, 2019 4:05 PM
> To: Iremonger, Bernard ; Thomas Monjalon
>
> Cc: dev@dpdk.org; Ananyev, Konstantin ;
> ano...@marvell.com; jer...@marvell.com
> Subject: RE: [PATCH v2 0/3] examples/ipsec-secgw: set default
>
> > > > > Hi All,
> > > > >
> > > > > This patchset would need ack from more vendors as it will impact
> > > > > user
> > > > experience
> > > > > on a key example application which is normally demonstrated to
> > > customers.
> > > > >
> > > > > IPSec library is still evolving and there are new
Hi Akhil,
Marvell is NOT OK with this change in this cycle. The library is still emerging
and the boundary between ipsec-secgw and lib ipsec still hasn't emerged
clearly. Moreover, lib_ipsec mode isn't even working with the default conf (I
believe the fix for this still in discussion. The issue
> > >
> > > 11/10/2019 14:40, Akhil Goyal:
> > > > Hi All,
> > > >
> > > > This patchset would need ack from more vendors as it will impact
> > > > user
> > > experience
> > > > on a key example application which is normally demonstrated to
> > customers.
> > > >
> > > > IPSec library is still e
Hi Akhil,
> -Original Message-
> From: Akhil Goyal [mailto:akhil.go...@nxp.com]
> Sent: Tuesday, October 15, 2019 7:43 AM
> To: Thomas Monjalon
> Cc: Iremonger, Bernard ; dev@dpdk.org;
> Ananyev, Konstantin ;
> ano...@marvell.com; jer...@marvell.com
> Subject: RE: [PATCH v2 0/3] examples/
>
> 11/10/2019 14:40, Akhil Goyal:
> > Hi All,
> >
> > This patchset would need ack from more vendors as it will impact user
> experience
> > on a key example application which is normally demonstrated to customers.
> >
> > IPSec library is still evolving and there are new functionality added ev
11/10/2019 14:40, Akhil Goyal:
> Hi All,
>
> This patchset would need ack from more vendors as it will impact user
> experience
> on a key example application which is normally demonstrated to customers.
>
> IPSec library is still evolving and there are new functionality added every
> release.
Hi Akhil,
With this patch applied the legacy code path in the ipsec-secgw application is
still available. The default code path is now to use librte_ipsec.
The "-l 0" option at startup allows the legacy code path to be used.
Both code paths are still available.
Regards,
Bernard
> -Origina
Hi All,
This patchset would need ack from more vendors as it will impact user experience
on a key example application which is normally demonstrated to customers.
IPSec library is still evolving and there are new functionality added every
release.
Atleast from NXP side we are not OK with this ch
> -Original Message-
> From: Iremonger, Bernard
> Sent: Wednesday, October 2, 2019 10:00 AM
> To: Ananyev, Konstantin ; dev@dpdk.org;
> akhil.go...@nxp.com
> Subject: RE: [PATCH v2 0/3] examples/ipsec-secgw: set default
>
> Hi Konstantin,
>
> > -Original Message-
> > From: Ana
Hi Konstantin,
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Tuesday, October 1, 2019 6:31 PM
> To: Iremonger, Bernard ; dev@dpdk.org;
> akhil.go...@nxp.com
> Subject: RE: [PATCH v2 0/3] examples/ipsec-secgw: set default
>
>
> Hi Bernard,
>
> >
> > This patch set, sets the de
Hi Bernard,
>
> This patch set, sets the default code path in the ipsec-secgw
> application to use the librte_ipsec.
> The *_old test scripts have been modified to use the legacy code
> path.
>
> Changes in v2:
> -
> The error messages for the -l option have been updated.
> The pkt
This patch set, sets the default code path in the ipsec-secgw
application to use the librte_ipsec.
The *_old test scripts have been modified to use the legacy code
path.
Changes in v2:
-
The error messages for the -l option have been updated.
The pktest.sh script has been updated to d
19 matches
Mail list logo
