DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	Paul Emmerich <emmericp@net.in.tum.de>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Performance regression in DPDK 1.8/2.0
Date: Tue, 28 Apr 2015 11:32:32 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89727297FA3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20150428105505.GA7484@bricha3-MOBL3>



> -----Original Message-----
> From: Richardson, Bruce
> Sent: Tuesday, April 28, 2015 11:55 AM
> To: Paul Emmerich
> Cc: De Lara Guarch, Pablo; dev@dpdk.org
> Subject: Re: [dpdk-dev] Performance regression in DPDK 1.8/2.0
> 
> On Tue, Apr 28, 2015 at 12:43:16PM +0200, Paul Emmerich wrote:
> > Hi,
> >
> > sorry, I mixed up the hardware I used for my tests.
> >
> >
> > Paul Emmerich <emmericp@net.in.tum.de>:
> > > CPU: Intel(R) Xeon(R) CPU E3-1230 v2
> > > TurboBoost and HyperThreading disabled.
> > > Frequency fixed at 3.30 GHz via acpi_cpufreq.
> >
> > The CPU frequency was fixed at 1.60 GHz to enforce
> > a CPU bottleneck.
> >
> >
> > My original post said that I used a Xeon E5-2620 v3
> > at 1.2 GHz, this is incorrect. The calculation for Cycles/Pkt
> > in the original post used the correct 1.6 GHz figure, though.
> >
> > (I used the E5 CPU for the evaluation of my packet generator
> > performance with 1.7.1/2.0.0, not for the l2fwd test.)

Thanks for the update. So, just for clarification, 
for l2fwd you used E3-1230 v2 (Ivy Bridge), at 1.6 GHz or 3.3 GHz?

Pablo
> >
> >
> > Sorry for the confusion.
> >
> >
> > Paul
> Thanks for the update - we are investigating.
> 
> /Bruce

  reply	other threads:[~2015-04-28 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 18:50 Paul Emmerich
2015-04-27  8:06 ` Pavel Odintsov
2015-04-27 17:38   ` De Lara Guarch, Pablo
2015-04-27 22:28     ` Paul Emmerich
2015-04-28  5:50       ` Matthew Hall
2015-04-28 10:56         ` Paul Emmerich
2015-04-28 10:43       ` Paul Emmerich
2015-04-28 10:55         ` Bruce Richardson
2015-04-28 11:32           ` De Lara Guarch, Pablo [this message]
2015-04-28 10:58       ` Bruce Richardson
2015-04-28 11:31       ` De Lara Guarch, Pablo
2015-04-28 11:48         ` Paul Emmerich
2015-05-05 14:56           ` De Lara Guarch, Pablo

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=E115CCD9D858EF4F90C690B0DCB4D89727297FA3@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=emmericp@net.in.tum.de \
    /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).