All of lore.kernel.org
 help / color / mirror / Atom feed
From: jozsef imrek <imrek@atomki.hu>
To: linuxppc-embedded@ozlabs.org
Cc: rick.moleres@xilinx.com
Subject: RE: Speed of plb_temac 3.00 on ML403
Date: Fri, 9 Feb 2007 15:57:15 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0702091527440.32063@imrek.org> (raw)
In-Reply-To: <BAY110-F38826CD4A177B058C34CFFB29C0@phx.gbl>

On Fri, 9 Feb 2007, Ming Liu wrote:

> Now with my system(plb_temac and hard_temac v3.00 with all features enabled 
> to improve the performance, Linux 2.6.10, 300Mhz ppc, netperf), I can achieve 
> AT MOST 213.8Mbps for TCP TX and 277.4Mbps for TCP RX, when jumbo-frame is 
> enabled as 8500. For UDP it is 350Mbps for TX, also 8500 jumbo-frame is 
> enabled. 
> So it looks that my results are still much less than yours from 
> Xilinx(550Mbps TCP TX). So I am trying to find the bottleneck and improve the 
> performance.


when testing network performance you might want to use the packet
generator included in the 2.6 linux kernel (in menuconfig go to
Networking -> Networking options -> Network testing -> Packet Generator).

with this tool you can bypass the ip stack, user space/kernel space 
barrier, etc, and measure the speed of the hardware itself using UDP-like
packets.

using pktgen i have seen data rates close to gigabit. (the hardware i'm 
working with is a memec minimodule with V4FX12. i'm using plb_temac with
s/g dma, plb running at 100MHz, and our custom core accessed via IPIF's
address range. sw is linux 2.6.19, xilinx tools are EDK 8.2i)



another hint: when transfering bulk amount of data TCP is probably an
overkill, especially on dedicated intranets and given the reliability
of the network devices available today. just use UDP if you can.


-- 
mazsi

----------------------------------------------------------------
strawberry fields forever!                       imrek@atomki.hu
----------------------------------------------------------------

  reply	other threads:[~2007-02-09 14:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 19:08 Speed of plb_temac 3.00 on ML403 Rick Moleres
2006-12-12 11:08 ` Ming Liu
2007-02-09 14:16 ` Ming Liu
2007-02-09 14:57   ` jozsef imrek [this message]
2007-02-11 15:25     ` Ming Liu
2007-02-12 18:09       ` jozsef imrek
2007-02-12 19:18         ` Ming Liu
2007-02-14  7:24           ` jozsef imrek
2007-02-09 16:00   ` Rick Moleres
2007-02-11  6:22     ` Leonid
2007-02-11 13:37     ` Ming Liu
2007-02-12 19:45       ` Rick Moleres
2007-02-12 20:39         ` Ming Liu
2007-02-11  6:55   ` Linux " Leonid
2007-02-11 13:10     ` Ming Liu
  -- strict thread matches above, loose matches on Subject: below --
2006-12-13  0:11 Speed of plb_temac 3.00 " Rick Moleres
2006-12-17 15:05 ` Ming Liu
2006-12-05 16:18 Thomas Denzinger
2006-12-05 16:49 ` Ming Liu
2006-12-05 18:42 ` Michael Galassi

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=Pine.LNX.4.61.0702091527440.32063@imrek.org \
    --to=imrek@atomki.hu \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rick.moleres@xilinx.com \
    /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.