From: Ookhoi <ookhoi@dds.nl>
To: Jordan Mendelson <jordy@napster.com>
Cc: "David S. Miller" <davem@redhat.com>, Vibol Hou <vibol@khmer.cc>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
sim@stormix.com
Subject: Re: 2.4 tcp very slow under certain circumstances (Re: netdev issues (3c905B))
Date: Thu, 22 Feb 2001 09:28:02 +0100 [thread overview]
Message-ID: <20010222092802.B405@humilis> (raw)
In-Reply-To: <HDEBKHLDKIDOBMHPKDDKMEGDEFAA.vibol@khmer.cc> <20010221104723.C1714@humilis> <14995.40701.818777.181432@pizda.ninka.net> <3A94418D.A0DD99BF@napster.com>
In-Reply-To: <3A94418D.A0DD99BF@napster.com>; from jordy@napster.com on Wed, Feb 21, 2001 at 02:30:37PM -0800
Hi Jordan,
> > > We have exactly the same problem but in our case it depends on the
> > > following three conditions: 1, kernel 2.4 (2.2 is fine), 2, windows ip
> > > header compression turned on, 3, a free internet access provider in
> > > Holland called 'Wish' (which seemes to stand for 'I Wish I had a faster
> > > connection').
> > > If we remove one of the three conditions, the connection is oke. It is
> > > only tcp which is affected.
> > > A packet on its way from linux server to windows client seems to get
> > > dropped once and retransmitted. This makes the connection _very_ slow.
> >
> > :-( I hate these buggy systems.
> >
> > Does this patch below fix the performance problem and are the windows
> > clients win2000 or win95?
>
> I wanted to see if this would fix the problem I was seeing with Win9x
> users on PPP w/ compression dialing up to Earthlink in the bay area
> (there are others, but it's the only one I can reproduce).
>
> I compiled 2.4.1 with this change and for some odd reason, the kernel
> started dropping packets and became unusable (couldn't ssh in) after
> around 4050 connections were opened. I tested it also with 2.4.1-ac20
> and had the same problem right around 4050 connections.
>
> This is on a VA Linux box with dual eepro100's (one used) connected to a
> Cisco 6509.
I patched two computers, 2.4.1-ac20. One of them is a fairly loaded
webserver. Both have an uptime of 15.15 and 16.30 hours, and are fine.
Didn't test with that much connections though.
Ookhoi
next prev parent reply other threads:[~2001-02-22 8:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 0:06 netdev issues (3c905B) Vibol Hou
2001-02-21 0:21 ` Martin Moerman
2001-02-21 0:34 ` Vibol Hou
2001-02-21 9:47 ` 2.4 tcp very slow under certain circumstances (Re: netdev issues (3c905B)) Ookhoi
2001-02-21 13:12 ` Gregory Maxwell
2001-02-21 10:57 ` David S. Miller
2001-02-21 11:33 ` Ookhoi
2001-02-21 17:17 ` Ookhoi
2001-02-21 19:06 ` Vibol Hou
2001-02-21 19:22 ` Vibol Hou
2001-02-21 22:30 ` Jordan Mendelson
2001-02-22 8:28 ` Ookhoi [this message]
2001-02-21 23:49 ` Jordan Mendelson
2001-02-21 23:52 ` David S. Miller
2001-02-22 0:10 ` Jordan Mendelson
2001-02-22 0:50 ` Jordan Mendelson
2001-02-27 0:21 ` Simon Kirby
2001-02-27 0:26 ` David S. Miller
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=20010222092802.B405@humilis \
--to=ookhoi@dds.nl \
--cc=davem@redhat.com \
--cc=jordy@napster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sim@stormix.com \
--cc=vibol@khmer.cc \
/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).