From: "David S. Miller" <davem@redhat.com>
To: Jordan Mendelson <jordy@napster.com>
Cc: ookhoi@dds.nl, Vibol Hou <vibol@khmer.cc>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
sim@stormix.com, netdev@oss.sgi.com
Subject: Re: 2.4 tcp very slow under certain circumstances (Re: netdev issues (3c905B))
Date: Wed, 21 Feb 2001 15:52:37 -0800 (PST) [thread overview]
Message-ID: <14996.21701.542448.49413@pizda.ninka.net> (raw)
In-Reply-To: <3A9453F4.993A9A74@napster.com>
In-Reply-To: <HDEBKHLDKIDOBMHPKDDKMEGDEFAA.vibol@khmer.cc> <20010221104723.C1714@humilis> <14995.40701.818777.181432@pizda.ninka.net> <3A9453F4.993A9A74@napster.com>
Jordan Mendelson writes:
> Now, if it didn't have the side effect of dropping packets left and
> right after ~4000 open connections (simultaneously), I could finally
> move our production system to 2.4.x.
There is no reason my patch should have this effect.
All of this is what appears to be a bug in Windows TCP header
compression, if the ID field of the IPv4 header does not change then
it drops every other packet.
The change I posted as-is, is unacceptable because it adds unnecessary
cost to a fast path. The final change I actually use will likely
involve using the TCP sequence numbers to calculate an "always
changing" ID number in the IPv4 headers to placate these broken
windows machines.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-02-21 23:55 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
2001-02-21 23:49 ` Jordan Mendelson
2001-02-21 23:52 ` David S. Miller [this message]
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=14996.21701.542448.49413@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jordy@napster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=ookhoi@dds.nl \
--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).