From: Harry Edmon <harry@atmos.washington.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: Network slowdown from 2.6.7 to 2.6.9
Date: Tue, 23 Nov 2004 15:41:58 -0800 [thread overview]
Message-ID: <41A3CAC6.1020004@atmos.washington.edu> (raw)
In-Reply-To: <20041123100450.3cbb82e6@zqx3.pdx.osdl.net>
I tried the new e1000 driver with TSO off and tcp_rmem set to a max of
1000000 (I am sure the problem is reading and not writing). It had no
effect. The TCP traffic on the system is via RCP calls to port 388.
Any other ideas?
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.
>
>
next prev parent reply other threads:[~2004-11-23 23:44 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
2004-11-23 23:41 ` Harry Edmon [this message]
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=41A3CAC6.1020004@atmos.washington.edu \
--to=harry@atmos.washington.edu \
--cc=linux-kernel@vger.kernel.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