All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mahan <mahan-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: 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

             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]
     [not found] ` <519F74F6.3000903-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-05-24 14:41   ` Best example for showing throughput? Thomas Monjalon
     [not found]     ` <201305241641.38896.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-24 15:45       ` Thomas Monjalon
     [not found]         ` <201305241745.25844.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-24 18:51           ` Patrick Mahan
     [not found]             ` <5BBC85C7-B39F-4200-AB7B-CD5464BDA431-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-05-25 19:23               ` Damien Millescamps
     [not found]                 ` <51A10FC3.5050703-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-25 20:59                   ` Damien Millescamps
     [not found]                     ` <51A12618.3040509-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-28 19:15                       ` Patrick Mahan
     [not found]                         ` <CB827065-95E8-4267-B00F-BE1F3B59316F-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-05-29 14:07                           ` Damien Millescamps
     [not found]                             ` <51A60BA0.7000700-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-29 18:24                               ` Patrick Mahan
2013-05-24 18:32       ` Patrick Mahan
     [not found]         ` <E95E374C-A66A-43C8-9BFC-1940BC0BC2E8-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-05-24 20:03           ` Olivier MATZ
     [not found]             ` <519FC787.4090006-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
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-5dhxhckeavbytjvyw6ydsg@public.gmane.org \
    --cc=dev-VfR2kkLFssw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.