From: Matthew Hall <mhall@mhcomputing.net>
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: Mon, 27 Apr 2015 22:50:55 -0700 [thread overview]
Message-ID: <0B4E9314-9F6A-4AE6-8B1F-B41F9A5264B1@mhcomputing.net> (raw)
In-Reply-To: <23D2CA18-1875-4182-8DEE-9F6393011D2C@net.in.tum.de>
On Apr 27, 2015, at 3:28 PM, Paul Emmerich <emmericp@net.in.tum.de> wrote:
> Let me know if you need any additional information.
> I'd also be interested in the configuration that resulted in the 20% speed-
> up that was mentioned in the original mbuf patch
Not sure if it's relevant or not, but there was another mail claiming PCIe MSI-X wasn't necessarily working in DPDK 2.x. Not sure if that could be causing slowdowns when there are drastic volumes of 64-byte packets causing a lot of PCI activity.
Also, you are mentioning some specific patches were involved... so I have to ask if anybody tried git bisect yet or not. Maybe easier than trying to guess at the answer.
Matthew.
next prev parent reply other threads:[~2015-04-28 5:50 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 [this message]
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
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=0B4E9314-9F6A-4AE6-8B1F-B41F9A5264B1@mhcomputing.net \
--to=mhall@mhcomputing.net \
--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).