From: Brian Bloniarz <bmb@athenacr.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: dormando <dormando@rydia.net>,
netdev@vger.kernel.org, Rick Jones <rick.jones2@hp.com>,
shemminger@osdl.org
Subject: [PATCH iproute2] document initcwnd
Date: Wed, 05 May 2010 21:37:40 -0400 [thread overview]
Message-ID: <4BE21D64.4040600@athenacr.com> (raw)
In-Reply-To: <20100505150343.0c09c6ba@nehalam>
Stephen Hemminger wrote:
> On Wed, 05 May 2010 16:56:34 -0400
> Brian Bloniarz <bmb@athenacr.com> wrote:
>
>> dormando wrote:
>>>> 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 :)
>> Documenting the flag in ip(8) might increase its visibility
>> a little. I don't see it documented in the iproute2 git head,
>> though it shows up on http://linux.die.net/man/8/ip somehow.
>>
>> Stephen, do you know why that is?
>
> No one sent me an official patch to change it?
Mention initcwnd in ip(8). Text taken from doc/ip-cref.tex.
Signed-off-by: Brian Bloniarz <bmb@athenacr.com>
diff --git a/man/man8/ip.8 b/man/man8/ip.8
index a5d2915..777a0a7 100644
--- a/man/man8/ip.8
+++ b/man/man8/ip.8
@@ -211,7 +211,9 @@ replace " | " monitor " } "
.B realms
.IR REALM " ] [ "
.B rto_min
-.IR TIME " ]"
+.IR TIME " ] [ "
+.B initcwnd
+.IR NUMBER " ]"
.ti -8
.IR TYPE " := [ "
@@ -1561,6 +1563,13 @@ the clamp for congestion window. It is ignored if the
flag is not used.
.TP
+.BI initcwnd " NUMBER " "(2.5.70+ only)"
+Initial congestion window size for connections to this destination.
+Actual window size is this value multiplied by the MSS
+(``Maximal Segment Size'') for same connection. The default is
+zero, meaning to use the values specified in RFC2414.
+
+.TP
.BI advmss " NUMBER " "(2.3.15+ only)"
the MSS ('Maximal Segment Size') to advertise to these
destinations when establishing TCP connections. If it is not given,
next prev parent reply other threads:[~2010-05-06 1:37 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
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 ` Brian Bloniarz [this message]
2010-05-06 2:33 ` [PATCH iproute2] document initcwnd 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=4BE21D64.4040600@athenacr.com \
--to=bmb@athenacr.com \
--cc=dormando@rydia.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=shemminger@osdl.org \
--cc=shemminger@vyatta.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.