From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>,
"Qiu, Michael" <michael.qiu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: increase lookup burst size to 8
Date: Fri, 24 Jul 2015 01:14:00 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C7D4C20@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E01D911EF@shsmsx102.ccr.corp.intel.com>
> -----Original Message-----
> From: Xu, Qian Q
> Sent: Friday, July 24, 2015 2:09 AM
> To: De Lara Guarch, Pablo; Qiu, Michael; dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] examples/l3fwd: increase lookup burst size
> to 8
>
> And this patch will be only related to exact match, the common usage of lpm
> is not impacted.
That is right, thanks for pointing it out, Qian!
Pablo
>
> Thanks
> Qian
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Friday, July 24, 2015 8:29 AM
> To: Qiu, Michael; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: increase lookup burst size
> to 8
>
> Hi Michael,
>
> > -----Original Message-----
> > From: Qiu, Michael
> > Sent: Thursday, July 23, 2015 6:26 PM
> > To: De Lara Guarch, Pablo; dev@dpdk.org
> > Subject: RE: [dpdk-dev] [PATCH] examples/l3fwd: increase lookup burst
> > size to 8
> >
> > Hi, Pablo
> >
> > Is there any performance data for this change?
>
> With this change, performance increases around 12% compared to the
> version before the patch.
>
> Thanks,
> Pablo
>
> >
> > Thanks,
> > Michael
> >
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> > Sent: Thursday, July 23, 2015 9:12 AM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] [PATCH] examples/l3fwd: increase lookup burst size
> > to 8
> >
> > With the new hash implementation, the minimum lookup burst size to get
> > good performance is 8, since its internal pipeline consists of 4
> > stages of 2 entries each, so to avoid duplication, burst size should be 8 or
> more entries.
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2015-07-24 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 16:12 Pablo de Lara
2015-07-23 17:25 ` Qiu, Michael
2015-07-24 0:28 ` De Lara Guarch, Pablo
2015-07-24 1:08 ` Xu, Qian Q
2015-07-24 1:14 ` De Lara Guarch, Pablo [this message]
2015-07-27 14:43 ` Thomas Monjalon
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=E115CCD9D858EF4F90C690B0DCB4D8973C7D4C20@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=michael.qiu@intel.com \
--cc=qian.q.xu@intel.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).