From: Simon Kirby <sim@netnation.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Jordan Mendelson <jordy@napster.com>,
ookhoi@dds.nl, Vibol Hou <vibol@khmer.cc>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: 2.4 tcp very slow under certain circumstances (Re: netdev issues (3c905B))
Date: Mon, 26 Feb 2001 16:21:07 -0800 [thread overview]
Message-ID: <20010226162107.A31575@netnation.com> (raw)
In-Reply-To: <HDEBKHLDKIDOBMHPKDDKMEGDEFAA.vibol@khmer.cc> <20010221104723.C1714@humilis> <14995.40701.818777.181432@pizda.ninka.net> <3A9453F4.993A9A74@napster.com> <14996.21701.542448.49413@pizda.ninka.net>
In-Reply-To: <14996.21701.542448.49413@pizda.ninka.net>; from davem@redhat.com on Wed, Feb 21, 2001 at 03:52:37PM -0800
On Wed, Feb 21, 2001 at 03:52:37PM -0800, David S. Miller wrote:
> 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.
Has such a patch gone in to the kernel yet?
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
next prev parent reply other threads:[~2001-02-27 0:21 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 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
2001-02-22 0:10 ` Jordan Mendelson
2001-02-22 0:50 ` Jordan Mendelson
2001-02-27 0:21 ` Simon Kirby [this message]
2001-02-27 0:26 ` David S. Miller
2001-02-21 13:12 ` Gregory Maxwell
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=20010226162107.A31575@netnation.com \
--to=sim@netnation.com \
--cc=davem@redhat.com \
--cc=jordy@napster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=ookhoi@dds.nl \
--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