All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan A. Dickey" <dan.dickey@savvis.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: Sridhar Samudrala <sri@us.ibm.com>, netdev@oss.sgi.com
Subject: Re: TCP Hang (or close to it):  Windows XP -> Linux (w/tcp_bic)
Date: Fri, 29 Oct 2004 13:21:25 -0500	[thread overview]
Message-ID: <200410291321.25723.dan.dickey@savvis.net> (raw)
In-Reply-To: <20041029110019.4f175979.davem@davemloft.net>

On Friday 29 October 2004 13:00, David S. Miller wrote:
> 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.

That's a good point.  I was concerned that it might be
playing a role in what window size got sent back to
the sending machine.  Glad to hear it's not a worry.
BTW - any idea if tcp_bic would be easily modified
to be configurable on a per interface basis?  We typically
have a 100Mb interface on a LAN; and another 100Mb
interface going out to a WAN (DS3 or E3).
We're using tcp_bic to get near 95+% utilization of the
WAN connection; but I don't think we need it on the LAN,
and in some situations it may interfere... or, is this not
a concern?  Thanks again all.

Sridhar,
thank's for the pointer.

I'll be updating to 2.6.9 and will let you know the
results of my testing.
 -Dan

-- 
Dan A. Dickey
dan.dickey@savvis.net

SAVVIS
Transforming Information Technology

      reply	other threads:[~2004-10-29 18:21 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
2004-10-29 18:21     ` Dan A. Dickey [this message]

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=200410291321.25723.dan.dickey@savvis.net \
    --to=dan.dickey@savvis.net \
    --cc=davem@davemloft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.