DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: 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, 5 May 2015 14:56:56 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8972729A5AD@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <C8F8FA83-ADCD-42D5-9F68-50F4E77E5DCA@net.in.tum.de>

Hi Paul,

> -----Original Message-----
> From: Paul Emmerich [mailto:emmericp@net.in.tum.de]
> Sent: Tuesday, April 28, 2015 12:48 PM
> To: De Lara Guarch, Pablo
> Cc: Pavel Odintsov; dev@dpdk.org
> Subject: Re: [dpdk-dev] Performance regression in DPDK 1.8/2.0
> 
> Hi,
> 
> 
> De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>:
> > Could you tell me which changes you made here? I see you are using
> simple tx code path on 1.8.0,
> > but with the default values, you should be using vector tx,
> > unless you have changed anything in the tx configuration.
> 
> sorry, I might have written that down wrong or read the output wrong.
> I did not modify the l2fwd example.
> 
> 
> > So, just for clarification,
> > for l2fwd you used E3-1230 v2 (Ivy Bridge), at 1.6 GHz or 3.3 GHz?
> 
> At 1.6 GHz as it is simply too fast at 3.3 GHz ;)
> 
> 
> I'll probably write a minimal example that shows my
> problem with tx only sometime next week.
> I just used the l2fwd example to illustrate my point
> with a 'builtin' example.

Thanks for the clarification. I tested it on Ivy Bridge as well, and I could not reproduce the issue.
Make sure that you use vector rx/tx anyway, to get best performance 
(you should be seeing better performance, since l2fwd in 1.8/2.0 uses both vector rx/tx).

Thanks,
Pablo

> 
> Paul

      reply	other threads:[~2015-05-05 14:57 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
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 [this message]

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=E115CCD9D858EF4F90C690B0DCB4D8972729A5AD@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@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).