From: Eric Dumazet <eric.dumazet@gmail.com>
To: chavey@google.com
Cc: davem@davemloft.net, netdev@vger.kernel.org, therbert@google.com,
joe@perches.com
Subject: Re: [PATCH] Add sysctl to set the advertised TCP initial receive window.
Date: Wed, 09 Dec 2009 21:33:16 +0100 [thread overview]
Message-ID: <4B20098C.8040102@gmail.com> (raw)
In-Reply-To: <pvmk4wvc3eb.fsf@chavey.mtv.corp.google.com>
Le 09/12/2009 21:13, chavey@google.com a écrit :
> Add a sysctl, tcp_init_rcv_wnd, to set the TCP initial receive window
> size advertised by passive and active TCP connections.
> The current Linux TCP implementation limits the advertised TCP initial
> receive window to the one prescribed by slow start. For short lived
> TCP connections used for transaction type of traffic (i.e. http
> requests), bounding the advertised TCP initial receive window results
> in increased latency to complete the transaction. There exists
> environments where strict adherence to using the TCP initial receive
> window used by slow start is un-necessary.
> The tcp_init_rcv_wnd sysctl allows increasing the TCP initial receive
> window for all TCP connections or on a per TCP connection, allowing
> for some of the TCP connection to advertise larger TCP receive window
> than the ones bounded by slow start. Support for setting initial
> congestion window is already supported in the stack but the feature
> is useless without the ability to set a larger initial receive window.
>
> Signed-off-by: Laurent Chavey <chavey@google.com>
> index f1813bc..7567edd 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -2248,6 +2248,11 @@ static int do_tcp_setsockopt(struct sock *sk, int level,
> break;
> #endif
>
> + case TCP_INIT_RCV_WND:
> + val = min_t(int, val, TCP_INIT_RCV_WND_MAX);
> + tp->rx_opt.init_rcv_wnd = val;
> + break;
> +
If user pass val = -1, you end with init_rcv_wnd = 255
Is it what you want ?
Probably not :)
Minor nit , your subject should be : [PATCH] tcp: Add sysctl to blablabla
next prev parent reply other threads:[~2009-12-09 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 20:13 [PATCH] Add sysctl to set the advertised TCP initial receive window chavey
2009-12-09 20:33 ` Eric Dumazet [this message]
2009-12-09 20:55 ` Joe Perches
2009-12-09 21:11 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2009-12-10 2:05 chavey
2009-12-10 16:57 ` Stephen Hemminger
2009-12-10 18:55 ` Joe Perches
2009-12-13 3:27 ` Eric W. Biederman
2009-12-09 0:30 chavey
2009-12-09 0:59 ` Joe Perches
2009-12-08 22:40 chavey
2009-12-08 23:00 ` Joe Perches
2009-12-09 13:26 ` Andi Kleen
2009-12-09 18:05 ` Tom Herbert
[not found] ` <65634d660912091001s44016cccq4f2422e613ba9db9@mail.gmail.com>
2009-12-10 2:21 ` David Miller
2009-12-10 21:55 ` Laurent Chavey
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=4B20098C.8040102@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=chavey@google.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@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 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.