From: Andi Kleen <andi@firstfloor.org>
To: chavey@google.com
Cc: davem@davemloft.net, netdev@vger.kernel.org, therbert@google.com
Subject: Re: [PATCH] Add sysctl to set the advertised TCP initial receive window.
Date: Wed, 09 Dec 2009 14:26:39 +0100 [thread overview]
Message-ID: <87fx7kmg6o.fsf@basil.nowhere.org> (raw)
In-Reply-To: <pvm638hum1a.fsf@chavey.mtv.corp.google.com> (chavey@google.com's message of "Tue, 08 Dec 2009 14:40:49 -0800")
chavey@google.com writes:
> 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 proscribed by slow start. For short leave
> 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.
That's not the Internet?
> 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.
Traditionally it was very discouraged to expose such settings to users.
There's the danger that lots of people will essentially turn off cwnd
without knowing what they're doing to "make downloads go faster", causing
problems in the public network.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-12-09 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 22:40 [PATCH] Add sysctl to set the advertised TCP initial receive window chavey
2009-12-08 23:00 ` Joe Perches
2009-12-09 13:26 ` Andi Kleen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-12-09 0:30 chavey
2009-12-09 0:59 ` Joe Perches
2009-12-09 20:13 chavey
2009-12-09 20:33 ` Eric Dumazet
2009-12-09 20:55 ` Joe Perches
2009-12-09 21:11 ` Eric Dumazet
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
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=87fx7kmg6o.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=chavey@google.com \
--cc=davem@davemloft.net \
--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 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).