From: Patrick Mahan <mahan@mahan.org>
To: dev@dpdk.org
Subject: [dpdk-dev] Best example for showing throughput?
Date: Fri, 24 May 2013 07:11:02 -0700 [thread overview]
Message-ID: <519F74F6.3000903@mahan.org> (raw)
Good morning,
I have been playing with this code now for about 2 weeks. I posted
earlier about being unable to get it to work on Fedora 14, but have
it working on CentOS 6.4. Here is my hardware -
Intel Xeon E5-2690 (8 physical, 16 virtual)
64 Gbyte DDR3 memory
Intel 82599EB-SPF dual port 10GE interface
CentOS 6.4 (2.6.32-358.6.1.el6.x86_64)
The 82599 is in a 16x PCI-e slot.
I have it attached to an IXIA box. I have been running the app 'testpmd'
in iofwd mode with 2K rx/tx descriptors and 512 burst/mbcache. I have been
varying the # of queues and unfortunately, I am not seeing full line rate.
I have CentOS booted to runlevel 3 (no X windows) and have turned off (I think)
all of the background processes I can.
I am seeing about 20-24% droppage on the receive side. It doesn't seem to
matter the # of queues.
Question 1: Is 'testpmd' the best application for this type of testing? If not,
which program? Or do I need to roll my own?
Question 2: I have blacklisted the Intel i350 ports on the motherboard and am
using ssh to access the platform. Could this be affecting the test?
Thoughts?
Thanks,
Patrick
next reply other threads:[~2013-05-24 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 14:11 Patrick Mahan [this message]
2013-05-24 14:41 ` Thomas Monjalon
2013-05-24 15:45 ` Thomas Monjalon
2013-05-24 18:51 ` Patrick Mahan
2013-05-25 19:23 ` Damien Millescamps
2013-05-25 20:59 ` Damien Millescamps
2013-05-28 19:15 ` Patrick Mahan
2013-05-29 14:07 ` Damien Millescamps
2013-05-29 18:24 ` Patrick Mahan
2013-05-24 18:32 ` Patrick Mahan
2013-05-24 20:03 ` Olivier MATZ
2013-05-24 20:44 ` Patrick Mahan
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=519F74F6.3000903@mahan.org \
--to=mahan@mahan.org \
--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).