From: rwhron@earthlink.net
To: scott.feldman@intel.com
Cc: netdev@oss.sgi.com
Subject: RE: 82540EM very slow on 2.6.0-test[45]
Date: Wed, 10 Sep 2003 21:14:43 -0400 [thread overview]
Message-ID: <20030911011443.GA22440@rushmore> (raw)
>> ftp'ing a multi-megabyte file gives about 16-20k/second
>> throughput. The destination machine was running Solaris 8.
> Linux -> Solaris
Linux doing an ftp put on Solaris.
>> This is a dual boot Dell P4. XP is about 1000x faster for
>> an ftp xfer, so the network seems okay.
> Is this Linux -> XP or XP -> Solaris? Trying to eliminate one player.
Linux ftp put to Solaris is slow. When booted into XP, ftp put to
Solaris is fast. Solaris -> Solaris is fast too.
> What about Linux -> Linux? Is that slow?
I will try that and some other combinations.
>> dmesg shows "e1000: eth0 NIC Link is Up 100 Mbps Full Duplex".
> This feels like a duplex mis-match.
Could well be. On our LAN, Solaris often has to be forced full-duplex
because auto-negotiate to the switches gives half-duplex. The ftp server
is full duplex. The client and server are on different segments.
I'll check if the PC is using correct duplex/speed for it's segment.
> Are you using the same cable for the different tests?
Yes. Same cable, same PC. I swapped CAT5 cables, but that didn't
change throughput.
Thanks for the suggestions!
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2003-09-11 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 1:14 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 21:40 82540EM very slow on 2.6.0-test[45] Feldman, Scott
2003-09-11 22:19 ` Ben Greear
2003-09-11 21:06 rwhron
2003-09-11 0:28 Feldman, Scott
2003-09-10 23:35 rwhron
2003-09-14 17:23 ` Florian Zwoch
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=20030911011443.GA22440@rushmore \
--to=rwhron@earthlink.net \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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).