From: "Ming Liu" <eemingliu@hotmail.com>
To: rick.moleres@xilinx.com
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Speed of plb_temac 3.00 on ML403
Date: Fri, 09 Feb 2007 14:16:43 +0000 [thread overview]
Message-ID: <BAY110-F38826CD4A177B058C34CFFB29C0@phx.gbl> (raw)
In-Reply-To: <689CB232690D8D4E97DA6C76DA098E6C0360F790@XCO-EXCHVS1.xlnx.xilinx.com>
Dear Rick,
Again the problem of TEMAC speed. Hopefully you can give me some suggestion
on that.
>With a 300Mhz system we saw about 730Mbps Tx with TCP on 2.4.20
>(MontaVista Linux) and about 550Mbps Tx with TCP on 2.6.10 (MontaVista
>again) - using netperf w/ TCP_SENDFILE option. We didn't investigate the
>difference between 2.4 and 2.6.
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 I use netperf to transfer data, I noticed that the CPU utilization is
almost 100%. So I suspect that CPU is the bottleneck. However other friends
said the PLB structure is the bottleneck, because when the CPU is lowered
to 100Mhz, the performance will not change much, but if the PLB frquency is
lowered, it will. Then they conclude that with the PLB structure, the CPU
will wait a long time to load and store data from DDR. So PLB is the
criminal.
Then come some questions. 1. Is your result from the GSRD structure or just
the normal PLB_TEMAC? Will the GSRD achieve a better performance than the
normal PLB_TEMAC? 2. Which on earch is the bottleneck for the network
performance, CPU or PLB structure? Is that possible for PLB to achieve a
much higher throughput? 3. Because your result is based on Montavista
Linux. Is there any difference between MontaVista Linux and the general
open-source linux kernel which could lead to different performance?
I know that many persons including me are struggling to improve the
performance of PLB_TEMAC on ML403. So please give us some hints and
suggestions with your experience and research. Thanks so much for your
work.
BR
Ming
_________________________________________________________________
与联机的朋友进行交流,请使用 MSN Messenger: http://messenger.msn.com/cn
next prev parent reply other threads:[~2007-02-09 14:16 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 [this message]
2007-02-09 14:57 ` jozsef imrek
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=BAY110-F38826CD4A177B058C34CFFB29C0@phx.gbl \
--to=eemingliu@hotmail.com \
--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.