From: "Allen Curtis" <acurtis@onz.com>
To: "Jean-Denis Boyer" <jdboyer@mediatrix.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Debugging Network Performance
Date: Wed, 5 Jun 2002 06:35:57 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFOECJDIAA.acurtis@onz.com> (raw)
In-Reply-To: <F1BED55F35F4D3118C0F00E0295CFF4DFFA05C@mail.mediatrix.com>
> With my 200MHz 8260 based board, using kernel 2.4.19-pre7,
> I fetch a large file (~50Mb) with ftp, and send it to /dev/null
> get large_file /dev/null
> and I obtain the following performance:
> 50216878 bytes received in 5.52 seconds (9090508 bytes/s)
I will check smaller files. I know that there is a nice burst of activity
when the transfer starts. Can you try 100MB+ transfer and see if you still
get the same performance. Perhaps I should try 2.4.19pre7. If I get better
results it sure helps to narrow the search for likely suspects. I will also
try piping to /dev/null.
> If the performance drops in 100Mbps full duplex, the problem might be
> one of configuration between your BCM switch and the external switch.
> Are both ends of the link (between your BCM switch and external switch)
> set to auto-negotiation?
The switch is a LinkSys 5 port 10/100 switch. (no configuration options that
I am aware of) All ports on the BCM should be in auto-negotiate mode. In a
previous version I printed the negotiation status of each port and it showed
100, full-duplex.
Thanks for the pointers. Based on the emails that I have received, I am not
the only one with this problem. Hopefully we can reproduce your results and
provide some feedback to the group.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-05 13:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 12:18 Debugging Network Performance Jean-Denis Boyer
2002-06-05 13:35 ` Allen Curtis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 5:18 Bill Fink
2002-06-05 13:16 ` Allen Curtis
2002-06-05 13:56 ` Bill Fink
2002-06-04 14:35 Mark Wisner
2002-06-04 14:46 ` Allen Curtis
2002-06-04 15:05 ` Michael Fischer
2002-06-04 11:12 Mark Wisner
2002-06-04 13:30 ` Allen Curtis
2002-06-04 4:34 Allen Curtis
2002-06-04 9:50 ` Kenneth Johansson
2002-06-04 3:27 Allen Curtis
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=NCBBIINEHIPFGJPLBEIFOECJDIAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=jdboyer@mediatrix.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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).