dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Paul Emmerich <emmericp-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Performance regression in DPDK 1.8/2.0
Date: Tue, 28 Apr 2015 11:55:06 +0100	[thread overview]
Message-ID: <20150428105505.GA7484@bricha3-MOBL3> (raw)
In-Reply-To: <47D837AA-FE82-45A1-AC3D-3CF600F5CC19-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org>

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-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org>:
> > 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.)
> 
> 
> Sorry for the confusion.
> 
> 
> Paul
Thanks for the update - we are investigating.

/Bruce

  parent reply	other threads:[~2015-04-28 10:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 18:50 Performance regression in DPDK 1.8/2.0 Paul Emmerich
     [not found] ` <6DC6DE50-F94F-419C-98DF-3AD8DCD4F69D-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org>
2015-04-27  8:06   ` Pavel Odintsov
     [not found]     ` <CALgsdbciDyJLm8Rp9GNbDb6sN=eCcFEVkWsSw95fvG32mYfqBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-27 17:38       ` De Lara Guarch, Pablo
     [not found]         ` <E115CCD9D858EF4F90C690B0DCB4D89727297ADB-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-04-27 22:28           ` Paul Emmerich
     [not found]             ` <23D2CA18-1875-4182-8DEE-9F6393011D2C-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org>
2015-04-28  5:50               ` Matthew Hall
     [not found]                 ` <0B4E9314-9F6A-4AE6-8B1F-B41F9A5264B1-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2015-04-28 10:56                   ` Paul Emmerich
2015-04-28 10:43               ` Paul Emmerich
     [not found]                 ` <47D837AA-FE82-45A1-AC3D-3CF600F5CC19-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org>
2015-04-28 10:55                   ` Bruce Richardson [this message]
2015-04-28 11:32                     ` De Lara Guarch, Pablo
2015-04-28 10:58               ` Bruce Richardson
2015-04-28 11:31               ` De Lara Guarch, Pablo
     [not found]                 ` <E115CCD9D858EF4F90C690B0DCB4D89727297F83-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-04-28 11:48                   ` Paul Emmerich
     [not found]                     ` <C8F8FA83-ADCD-42D5-9F68-50F4E77E5DCA-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org>
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=20150428105505.GA7484@bricha3-MOBL3 \
    --to=bruce.richardson-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=emmericp-mrRt1sWyIK0ZId6A0yLOdQ@public.gmane.org \
    /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).