From: "Bhupender Saharan" <bhupi.saharan@gmail.com>
To: "Mohammad Sadegh Sadri" <mamsadegh@hotmail.com>
Cc: Andrei Konovalov <akonovalov@ru.mvista.com>,
Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: ML403 gigabit ethernet bandwidth - 2.6 kernel
Date: Mon, 25 Jun 2007 04:52:50 -0700 [thread overview]
Message-ID: <720399a30706250452m4f04f6e6w1f0fdb4b0da76b12@mail.gmail.com> (raw)
In-Reply-To: <BAY115-W1188529D49F71948165AF6B2160@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 2193 bytes --]
Hi,
We need to findout where is the bottlenect.
1. Run vmstat on the ML403 board and find out the percentage CPU is busy
when you are transferring the file. That will show if cpu is busy or not.
2. Run oprofile and find out which are the routines eating away the cpu
time.
Once we have data from both the above routines, we can find out the
bottlenecks.
Regards
Bhupi
On 6/23/07, Mohammad Sadegh Sadri <mamsadegh@hotmail.com> wrote:
>
>
> Dear all,
>
> Recently we did a set of tests on performance of virtex 4FX hard TEMAC
> module using ML403
>
> we studied all of the posts here carefully: these are the system
> characteristics;
>
> Board : ML403
> EDK : EDK9.1SP2
> Hard TEMAC version and PLTEMAC version are both 3.0.a
> PPC clock frequency : 300MHz
> Kernel : 2.6.21-rc7 , downloaded from grant's git tree some thing near one
> week ago
> DMA type: 3 (sg dma)
> DRE : enabled for TX and RX, (2)
> CSUM offload is enabled for both of TX and RX
> tx and rx fifo sizes : 131072 bits
>
> the board comes up over NFS root file system completely and without any
> problems.
>
> PC system used for these tests is : CPU P4 Dual Core, 3.4GHz , 2Gigabytes
> memory, Dual gigabit ethernet port, running linux 2.6.21.3
> We have tested the PC system band width and it can easily reach 966mbits/s
> when connected to the same PC. ( using the same cross cable used for ml403
> test)
>
> Netperf is compiled with TCP SEND FILE enabled, ( -DHAVE_SENDFILE)
>
> (from board to PC)
> netperf -t TCP_SENDFILE -H 10.10.10.250 -F /boot/zImage.elf -- -m 16384 -s
> 87380 -S 87380
>
> the measured bandwidth for this test was just 40.66Mbits.
> It is also true for netperf from PC to board.
>
> we do not have any more idea about what we should do to improve the
> bandwidth.
> any help or ideas is appreciated...
>
> _________________________________________________________________
> Connect to the next generation of MSN Messenger
>
> http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
[-- Attachment #2: Type: text/html, Size: 2871 bytes --]
next prev parent reply other threads:[~2007-06-25 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 12:19 ML403 gigabit ethernet bandwidth - 2.6 kernel Mohammad Sadegh Sadri
2007-06-23 18:48 ` Ming Liu
2007-06-25 11:52 ` Bhupender Saharan [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-23 19:08 Mohammad Sadegh Sadri
2007-06-23 19:10 ` Ming Liu
2007-06-24 14:36 Mohammad Sadegh Sadri
2007-06-25 10:03 ` Ming Liu
2007-06-25 15:21 Glenn.G.Hart
2007-06-25 19:42 Greg Crocker
2007-06-26 7:42 ` Ming Liu
2007-06-26 14:53 Mohammad Sadegh Sadri
2007-06-26 18:12 ` Ming Liu
2007-07-04 15:17 Mohammad Sadegh Sadri
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=720399a30706250452m4f04f6e6w1f0fdb4b0da76b12@mail.gmail.com \
--to=bhupi.saharan@gmail.com \
--cc=akonovalov@ru.mvista.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mamsadegh@hotmail.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 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).