All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Millescamps <damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Best example for showing throughput?
Date: Sat, 25 May 2013 21:23:47 +0200	[thread overview]
Message-ID: <51A10FC3.5050703@6wind.com> (raw)
In-Reply-To: <5BBC85C7-B39F-4200-AB7B-CD5464BDA431-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>

On 05/24/2013 08:51 PM, Patrick Mahan wrote:
>> > 
>> > Are you sending and receiving on the 2 ports at the same time ?
>> > Forwarding in the 2 directions is equivalent to double the bandwidth.
>> > Maybe that 14.88*2 = 29.76 Mpps is too much for your hardware.
>> > 
> Yes I am running traffic both ways.  Interestingly, the amount of drops seem consistent in both directions.  This makes sense since testpmd is spinning off a thread to read from each input queue.
>
Hi Patrick,

If you are using both ports of the same Niantics at the same time then
you won't be able to reach the line-rate on both port. It is a
limitation of the PLX bridge on the board. The expected performance on
port 1 when port 0 is used at line-rate should be around 75% of the
line-rate from what I know.
Since you are forwarding packets from one port to another, the packet
dropped because of this will impact the performance on both ways since
what is dropped on port 1 won't be forwarded for obvious reasons, and
some of the packets from port 0 will be lost while trying to transmit
them on port 1. Eventually, you will end up with the lower performance
of the two ports which seems to be consistent with the performance you
report.

Hope this helps,
-- 
Damien

  parent reply	other threads:[~2013-05-25 19:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 14:11 Best example for showing throughput? Patrick Mahan
     [not found] ` <519F74F6.3000903-5dHXHCkEAVbYtjvyW6yDsg@public.gmane.org>
2013-05-24 14:41   ` 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 [this message]
     [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=51A10FC3.5050703@6wind.com \
    --to=damien.millescamps-pdr9zngts4eavxtiumwx3w@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.