From: "David S. Miller" <davem@davemloft.net>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: dan.dickey@savvis.net, netdev@oss.sgi.com
Subject: Re: TCP Hang (or close to it): Windows XP -> Linux (w/tcp_bic)
Date: Fri, 29 Oct 2004 11:00:19 -0700 [thread overview]
Message-ID: <20041029110019.4f175979.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0410291005100.3323@w-sridhar.beaverton.ibm.com>
On Fri, 29 Oct 2004 10:10:42 -0700 (PDT)
Sridhar Samudrala <sri@us.ibm.com> wrote:
> This looks like the same TCP window overflow problem in 2.6.7 that came up a
> couple of days back.
>
> See the thread
> http://marc.theaimsgroup.com/?t=109887532400001&r=1&w=2
> and the patch posted by davem.
Yes, and BTW for the original poster, BIC only effects sender
behavior whereas in your test case the Linux system with BIC
enabled is the receiver.
next prev parent reply other threads:[~2004-10-29 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 14:25 TCP Hang (or close to it): Windows XP -> Linux (w/tcp_bic) Dan A. Dickey
2004-10-29 17:10 ` Sridhar Samudrala
2004-10-29 18:00 ` David S. Miller [this message]
2004-10-29 18:21 ` Dan A. Dickey
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=20041029110019.4f175979.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dan.dickey@savvis.net \
--cc=netdev@oss.sgi.com \
--cc=sri@us.ibm.com \
/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).