public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: lnx-kern@soo.com
Cc: Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Network sky2 Module
Date: Tue, 18 Sep 2007 10:28:43 -0400	[thread overview]
Message-ID: <46EFE09B.6090901@tmr.com> (raw)
In-Reply-To: <46EF4DE1.4000707@soo.com>

ben soo wrote:
> i'm experiencing this problem myself.  i have 2 servers, one using 
> X86_64 kernel version 2.6.23-rc5 on a 100Mbit network and one with i386 
> kernel version 2.6.23-rc6 on a 1Gbit network.
> 
> They both have this issue with the sky2 network device driver whereby 
> the device would stop working and need to be brought down and back up.
> 
> On the X86_64 kernel on a 100Mbit network, this is a very occasional 
> thing, while on the i386 kernel on a 1Gbit network the device only works 
> for a few minutes at a time.  If i set the MTU to 7200 then the device 
> seems to stay functional, but then i see long delays when it's talking 
> to 100Mbit devices with standard 1500 MTU that are outside of its LAN 
> segment.
> 
> This last might be an artifact caused by the firewall, i dunno.
> 
Yes, I have found that I get far less problem in this area leaving the 
MTU at 1500, then putting a larger MTU (usually 9000) into the routing 
table for segments, or even just machines, where I know there is direct 
connectivity. I use 9000 MTU with my directly connected file server, 
1500 elsewhere. I can go to 9000 for nbd servers as well, assuming the 
connection doesn't pass a firewall.

I have some hints that while the switches I use will speak 10/100/1000 
between machines with different speeds, and will handle jumbo packets 
between machines at the same speed, if I'm going Gbit/jumbo to 
1500/slower performance seems to suffer more than talking smaller 
packets. That may be because window size needs to be even larger or 
something.

I have some legacy machines talking 10Mbit/half on 10base2 cable, I may 
be seeing more of this than the average site. That's legacy as in 
"attached to something expensive to replace."

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  reply	other threads:[~2007-09-18 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 15:14 PROBLEM: Network sky2 Module Werner Meurer
2007-09-18  4:02 ` ben soo
2007-09-18 14:28   ` Bill Davidsen [this message]
2007-09-18 15:05     ` Stephen Hemminger
2007-09-20  6:43       ` ben soo
2007-09-23  1:56         ` PROBLEM: Network sky2 Module, kernel version 2.6.23-rc7 ben soo
2007-09-24  6:06           ` Stephen Hemminger
2007-09-28 22:48           ` Bill Davidsen

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=46EFE09B.6090901@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnx-kern@soo.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