netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: rwhron@earthlink.net, netdev@oss.sgi.com
Subject: Re: 82540EM very slow on 2.6.0-test[45]
Date: Thu, 11 Sep 2003 15:19:32 -0700	[thread overview]
Message-ID: <3F60F4F4.2070107@candelatech.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E010124F030@orsmsx402.jf.intel.com>

Feldman, Scott wrote:
>>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).
> 
> 
> Maybe someone else on the list has some suggestions?  I think we're
> troubleshooting your network now.
> 
> Is it just ftp that's slow?  What's in the path between the Linux and
> the "slow" Solaris server?  Can you shorten the path?  What happens if
> you don't force 100/full on the "slow" Solaris server?

I know that Becker always yells and folks that force duplex.  It is
evidently not a good thing to do.

Also, I've seen linux ftp get very poor results when there is any
latency in the link.  That latency could include the solaris machine
reading from it's HD, etc.

Try saving the file locally to /dev/null, that takes at least one HD
out of the picture.  Also try using some network transfer tool that
does not read or write to disk.  I think ttcp might be good for that.

> 
> -scott
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2003-09-11 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 21:40 82540EM very slow on 2.6.0-test[45] Feldman, Scott
2003-09-11 22:19 ` Ben Greear [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-11 21:06 rwhron
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=3F60F4F4.2070107@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=netdev@oss.sgi.com \
    --cc=rwhron@earthlink.net \
    --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).