From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] examples/ipsec-secgw: set default
Date: Fri, 1 Nov 2019 13:19:48 +0000 [thread overview]
Message-ID: <VE1PR04MB66391B0D2A6542AA7D7F9F93E6620@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260E14C88@IRSMSX108.ger.corp.intel.com>
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 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 change.
> > > > >
> > > > > What can be changed in the library to make it acceptable as a
> > > > > default in this example?
> > > > >
> > > >
> > > > We are observing performance issues with ipsec library. So would
> > > > request other Vendors to confirm if they are OK with the performance
> > numbers.
> > >
> > > Could you give some details on the performance issues you are seeing.
> > >
> >
> > We were observing about 4-5% drop when using the ipsec-lib instead of the
> > Legacy code path. We would again measure it on RC1. That is why I say, I will
> > Hold this patch till RC2, unless some other vendor also confirms that.
>
> Is there any update on performance measurements on 19.11-rc1 ?
>
The performance impact of this patch is huge ~10% w.r.t. 19.11-rc1 base on NXP hardware.
We cannot merge this. Anoob also reported performance issues on Marvell hardware.
> Regards,
>
> Bernard.
next prev parent reply other threads:[~2019-11-01 13:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 8:59 [dpdk-dev] [PATCH 0/2] " Bernard Iremonger
2019-08-29 8:59 ` [dpdk-dev] [PATCH 1/2] examples/ipsec-secgw: set default to IPsec library mode Bernard Iremonger
2019-09-26 13:47 ` Ananyev, Konstantin
2019-09-26 13:51 ` Iremonger, Bernard
2019-08-29 8:59 ` [dpdk-dev] [PATCH 2/2] examples/ipsec-secgw: add -l 0 parameter to old scripts Bernard Iremonger
2019-09-26 13:43 ` Ananyev, Konstantin
2019-09-26 13:46 ` Iremonger, Bernard
2019-10-01 15:17 ` [dpdk-dev] [PATCH v2 0/3] examples/ipsec-secgw: set default Bernard Iremonger
2019-10-01 17:30 ` Ananyev, Konstantin
2019-10-02 8:59 ` Iremonger, Bernard
2019-10-02 9:11 ` Ananyev, Konstantin
2019-10-11 12:40 ` Akhil Goyal
2019-10-11 15:13 ` Iremonger, Bernard
2019-10-11 15:23 ` Thomas Monjalon
2019-10-15 6:42 ` Akhil Goyal
2019-10-15 8:54 ` Iremonger, Bernard
2019-10-15 15:05 ` Akhil Goyal
2019-10-16 10:44 ` Ananyev, Konstantin
2019-10-30 9:29 ` Iremonger, Bernard
2019-11-01 13:19 ` Akhil Goyal [this message]
2019-11-04 15:24 ` Ananyev, Konstantin
2019-11-05 8:01 ` Akhil Goyal
2019-11-05 9:10 ` Ananyev, Konstantin
2019-11-06 13:55 ` Anoob Joseph
2019-11-18 13:03 ` Ananyev, Konstantin
2019-10-16 4:18 ` Anoob Joseph
2019-10-01 15:17 ` [dpdk-dev] [PATCH v2 1/3] examples/ipsec-secgw: set default to IPsec library mode Bernard Iremonger
2019-10-14 13:53 ` Nicolau, Radu
2019-10-01 15:17 ` [dpdk-dev] [PATCH v2 2/3] examples/ipsec-secgw: add -l 0 parameter to old scripts Bernard Iremonger
2019-10-01 17:28 ` Ananyev, Konstantin
2019-10-14 13:55 ` Nicolau, Radu
2019-10-01 15:18 ` [dpdk-dev] [PATCH v2 3/3] examples/ipsec-secgw: update pktest.sh script Bernard Iremonger
2019-10-01 17:29 ` Ananyev, Konstantin
2019-10-14 13:56 ` Nicolau, Radu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=VE1PR04MB66391B0D2A6542AA7D7F9F93E6620@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).