From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"Hanoch Haim (hhaim)" <hhaim@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Ido Barnea (ibarnea)" <ibarnea@cisco.com>
Subject: Re: [dpdk-dev] DPDK 17.02 RC-3 performance degradation of ~10%
Date: Tue, 14 Feb 2017 13:38:44 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476D9FD5@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897476D9FA9@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Tuesday, February 14, 2017 1:28 PM
> To: Thomas Monjalon; Hanoch Haim (hhaim)
> Cc: dev@dpdk.org; Mcnamara, John; Ido Barnea (ibarnea)
> Subject: Re: [dpdk-dev] DPDK 17.02 RC-3 performance degradation of ~10%
>
> Hi,
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas
> Monjalon
> > Sent: Tuesday, February 14, 2017 1:05 PM
> > To: Hanoch Haim (hhaim)
> > Cc: dev@dpdk.org; Mcnamara, John; Ido Barnea (ibarnea)
> > Subject: Re: [dpdk-dev] DPDK 17.02 RC-3 performance degradation of
> ~10%
> >
> > 2017-02-14 12:19, Mcnamara, John:
> > > From: Hanoch Haim (hhaim)
> > > > We (trex traffic generator project) upgrade DPDK version from 16.07
> to
> > > > 17.02arc-3 and we experienced a performance degradation on the
> > following
> > > > NICS:
> > [...]
> > >
> > > Could you do a git-bisect to identify the change that caused this?
> >
> > +1 for the bisect.
> > Please could you try to isolate the change causing the regression?
>
> I reproduced the regression for i40e driver (3-4% degradation, not 10%).
> The commit that caused it was the following:
> 5ea0942129a4 ("net/i40e: add packet type metadata in vector Rx")
>
> This commit was introduced in 16.11, and not in 17.02. This caused some
> performance degradation
> in the i40e vector RX, due to the addition of packet type parsing in the
> PMD.
>
> Thanks,
> Pablo
Sorry, I was talking about RX and not TX, so this is probably not valid then.
Pablo
next prev parent reply other threads:[~2017-02-14 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 11:44 Hanoch Haim (hhaim)
2017-02-14 12:19 ` Mcnamara, John
2017-02-14 12:31 ` Hanoch Haim (hhaim)
2017-02-14 13:04 ` Thomas Monjalon
2017-02-14 13:28 ` De Lara Guarch, Pablo
2017-02-14 13:38 ` De Lara Guarch, Pablo [this message]
2017-02-15 12:35 ` Hanoch Haim (hhaim)
2017-06-21 21:24 Gudimetla, Leela Sankar
2017-06-21 22:06 Gudimetla, Leela Sankar
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=E115CCD9D858EF4F90C690B0DCB4D897476D9FD5@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=hhaim@cisco.com \
--cc=ibarnea@cisco.com \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.com \
/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).