From: dormando <dormando@rydia.net>
To: Brian Bloniarz <bmb@athenacr.com>
Cc: netdev@vger.kernel.org
Subject: Re: 3 packet TCP window limit?
Date: Wed, 5 May 2010 13:01:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.LNX.2.00.1005051239290.28957@d> (raw)
In-Reply-To: <4BE171EC.20904@athenacr.com>
> This sounds like TCP slow start.
>
> http://en.wikipedia.org/wiki/Slow-start
>
> As far as tunables you might want to play with the initcwnd route
> flag (see "ip route help")
Ah, yes, initcwnd was it. I'm well aware of TCP Congestion control / slow
start / etc. However I couldn't find the damn tunable for it :)
ssthresh/tso/etc didn't seem to unwedge it. Felt like describing it in the
most generic way possible would help :)
Other OS's appear to have a larger initcwnd. As do commercial load
balancers. The default of 3 seems to be tuned for 56k dialup modems. I'm a
little surprised that none of the pluggable TCP congestion control
algorithms changed this value. I went through all of them except for
tcp_yeah.
Anyway, thanks and sorry for the nearly off-topic post here. I see some
google papers on bumping initcwnd to 10... but I guess that's not linux's
deal yet.
next prev parent reply other threads:[~2010-05-05 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 9:10 3 packet TCP window limit? dormando
2010-05-05 13:26 ` Brian Bloniarz
2010-05-05 20:01 ` dormando [this message]
2010-05-05 20:23 ` Rick Jones
2010-05-05 21:31 ` dormando
2010-05-06 6:15 ` Lars Eggert
2010-05-06 8:51 ` dormando
[not found] ` <p2h349f35ee1005061513x1db24de0ld98a40256c481ac2@mail.gmail.com>
[not found] ` <q2ud1c2719f1005061613yf90cd7c6r46ee23cc49858e74@mail.gmail.com>
2010-05-06 23:15 ` Jerry Chu
2010-05-05 20:56 ` Brian Bloniarz
2010-05-05 22:03 ` Stephen Hemminger
2010-05-06 1:37 ` [PATCH iproute2] document initcwnd Brian Bloniarz
2010-05-06 2:33 ` Stephen Hemminger
2010-05-19 15:31 ` Stephen Hemminger
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=alpine.LNX.2.00.1005051239290.28957@d \
--to=dormando@rydia.net \
--cc=bmb@athenacr.com \
--cc=netdev@vger.kernel.org \
/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