From: Jun Han <junhanece@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] l2fwd/l3fwd performance drop of about 25% ?
Date: Tue, 25 Feb 2014 22:01:42 +0100 [thread overview]
Message-ID: <CAGeT4P+sumKdn-roauGBAaDf0p4NYxNRp=GOYxDsdKmcJwzVaQ@mail.gmail.com> (raw)
Hi all,
I have a quick question regarding the performance of DPDK l2fwd (Same
problem with l3fwd). I am seeing that when we start multiple ports (e.g.,
12 ports), for 64 byte packets, the RX rate is only at around 11 Mpps per
port, instead of 14.88 Mpps which is the line rate (with preablem+start of
delimeter + interframe gap). Do you know what could be the problem? I am
describing my experiment setup below.
Setup:
1. We have Intel Xeon E5-2680 (8 cores, 2.7GHz) dual socket, with 6x10GbE
Intel 82599EB dualport NICs (total of 12 ports). Machine A runs your
pktgen, and Machine B runs DPDK l2fwd, unmodified.
2. We are running pktgen on Machine A with the following command:
./app/build/pktgen -c ffff -n 4 --proc-type auto --socket-mem 1024,1024
--file-prefix pg -- -p 0xfff0 -P -m "1.0, 2.1, 3.2, 4.3, 8.4, 9.5, 10.6,
11.7, 12.8, 13.9, 14.10, 15.11"
3. We are running l2fwd on Machine B with the following command:
sudo ./build/l2fwd -c 0xff0f -n 4 -- -p 0xfff
Thank you very much in advance.
Jun
next reply other threads:[~2014-02-25 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 21:01 Jun Han [this message]
2014-02-27 9:36 ` Richardson, Bruce
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='CAGeT4P+sumKdn-roauGBAaDf0p4NYxNRp=GOYxDsdKmcJwzVaQ@mail.gmail.com' \
--to=junhanece@gmail.com \
--cc=dev@dpdk.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).