netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: chavey@google.com
Cc: shemminger@vyatta.com, netdev@vger.kernel.org, therber@google.com
Subject: Re: [PATCH] Add initrwnd to iproute2
Date: Tue, 15 Dec 2009 23:37:58 +0100	[thread overview]
Message-ID: <4B280FC6.7060003@gmail.com> (raw)
In-Reply-To: <pvmws0nricn.fsf@chavey.mtv.corp.google.com>

Le 15/12/2009 23:19, chavey@google.com a écrit :
> Add initrwnd option parsing to iproute. This option uses the new
> rtnetlink init_rcvwnd to set the TCP initial receive window size
> advertised by passive and active TCP connections.
> 
> Signed-off-by: Laurent Chavey <chavey@google.com>
> --
>  doc/ip-cref.tex           |    5 +++++
>  include/linux/rtnetlink.h |    2 ++
>  ip/iproute.c              |   13 ++++++++++++-
>  3 files changed, 19 insertions(+), 1 deletions(-)
> 
> diff --git a/doc/ip-cref.tex b/doc/ip-cref.tex
> index bb4eb78..30503c7 100644
> --- a/doc/ip-cref.tex
> +++ b/doc/ip-cref.tex
> @@ -1324,7 +1324,12 @@ peers are allowed to send to us.
>      If it is not given, Linux uses the value selected with \verb|sysctl|
>      variable \verb|net/ipv4/tcp_reordering|.
>  
> +\item \verb|initrwnd NUMBER|
>  
> +--- [2.5.70+ only] Initial receive window size for connections to 
> +    this destination. The actual window size is this value multiplied
> +    by the MSS (''Maximal Segment Size'') of the connection. The default
> +    value is zero, meaning to use Slow Start value.
>  

Maybe its true with google custom kernels, but for upstream, this is 2.6.33+ :)

  reply	other threads:[~2009-12-15 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 22:19 [PATCH] Add initrwnd to iproute2 chavey
2009-12-15 22:37 ` Eric Dumazet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-15 23:05 chavey
2009-12-26 19:08 ` Stephen Hemminger
2009-12-26 21:44   ` David Miller

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=4B280FC6.7060003@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=chavey@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=therber@google.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).