public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network slowdown from 2.6.7 to 2.6.9
Date: Tue, 23 Nov 2004 22:31:43 +0000	[thread overview]
Message-ID: <1101249103l.10296l.0l@werewolf.able.es> (raw)
In-Reply-To: <20041123100450.3cbb82e6@zqx3.pdx.osdl.net> (from shemminger@osdl.org on Tue Nov 23 19:04:50 2004)


On 2004.11.23, Stephen Hemminger wrote:
> On Mon, 22 Nov 2004 15:38:16 -0800
> Harry Edmon <harry@atmos.washington.edu> wrote:
> 
> > Tried them all - none of them helped.  Use "ntop" I can see that my 
> > throughput on the Intel gigabit ethernet interface on the system maxes 
> > out at 15.2 Mbps with 2.6.9.  With 2.6.7 it made it to 35 Mbps.
> > 
> > Does anyone have any other suggestions as to what to look for to 
> > diagnose this problem?
> 
> Well, before the TSO changes, if TSO was enabled then TCP would not obey slow
> start or do congestion control properly.  Did you increase the TCP send/receive
> buffers (sysctl's net.ipv4.tcp_rmem and net.ipv4.tcp_wmem)? You may just
> be window limited.  Also, 2.6.9 has TCP bugs with TSO that can cause panic's.
> These have been fixed in 2.6.10-rc2.
> 

With two 2.6.9 boxes (really, 2.6.9-mm1 and 2.6.9-bproc), I get this:

nada:~> iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 155.210.155.215 port 5001 connected with 155.210.155.212 port 41695
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   112 MBytes  94.0 Mbits/sec
annwn:/proc/sys/net> iperf -c nada
------------------------------------------------------------
Client connecting to nada, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[  3] local 155.210.155.212 port 41695 connected with 155.210.155.215 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   112 MBytes  94.0 Mbits/sec

So 94 Mbits/sec, through 100Mb ether. So parhaps the netsork layer
is not the culprit, just the driver.

BTW:

I'm getting an oops with 2.6.9 that ends on a call to skb_clone,
using e1000. Is this what you refer to ?

If the answer is yes, do you have any pointer to a patch to fix just
this ? I would prefer an individual patch instead of full -bk, because
I use 2.6.9+bproc, and probably bproc wont patch against -bk.

TIA.

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-rc2-jam3 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #1



  reply	other threads:[~2004-11-23 23:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 23:46 Network slowdown from 2.6.7 to 2.6.9 Harry Edmon
2004-11-17  0:32 ` Stephen Hemminger
2004-11-17  0:37   ` Con Kolivas
2004-11-17 19:25     ` Harry Edmon
2004-11-17 20:16       ` Martin Josefsson
2004-11-17 21:15         ` Harry Edmon
2004-11-17 21:44           ` Martin Josefsson
2004-11-22 23:38             ` Harry Edmon
2004-11-23 18:04               ` Stephen Hemminger
2004-11-23 22:31                 ` J.A. Magallon [this message]
2004-11-23 23:41                 ` Harry Edmon
2004-11-24  9:52                 ` Hans Kristian Rosbach
2004-11-24 17:55                   ` Stephen Hemminger
2004-11-25 15:08                     ` Alan Cox

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=1101249103l.10296l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@osdl.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