netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 11 Sep 2003 17:06:25 -0400	[thread overview]
Message-ID: <20030911210625.GA26764@rushmore> (raw)

> Is this Linux -> XP or XP -> Solaris?  Trying to eliminate one player.

The destination Solaris machine has an impact.  There are two
Solaris servers on the same subnet.  For one of the servers:

Solaris ftp put to linux is fast
Solaris ftp get from linux is slow
Linux ftp put to solaris is slow
Linux ftp get from solaris is slow

For the another Solaris 8 server on the same subnet,
all ftp xfer's with Linux machine are fast.  When the
machine is booted into XP, ftp is fast to either server.

>> dmesg shows "e1000: eth0 NIC Link is Up 100 Mbps Full Duplex".

> This feels like a duplex mis-match.

The Solaris server that is slow for most Linux ftp xfers has
100 MBPs full-duplex forced.  

The Solaris server that Linux talks to fast doesn't have
any duplex/capabilities forced.

I tried 4 Solaris servers.  2 had forced full duplex
and 100 Mbps.  Those are slow.  2 other Solaris servers
on the same LAN as the "slow" Solaris servers are fast.
These "fast" servers are using default settings (which
should also be 100 Mbps full-duplex).

The odd part is that XP will talk to all four Solaris
servers fast.

-- 
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html

             reply	other threads:[~2003-09-11 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 21:06 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  1:14 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=20030911210625.GA26764@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).