From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: brouer@redhat.com, netdev@vger.kernel.org, nanditad@google.com
Subject: Re: [PATCH] tcp: sysctl for initial receive window
Date: Fri, 21 Sep 2012 13:56:01 -0400 (EDT) [thread overview]
Message-ID: <20120921.135601.254379488076661898.davem@davemloft.net> (raw)
In-Reply-To: <1348241111.2669.580.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 21 Sep 2012 17:25:11 +0200
> On Fri, 2012-09-21 at 10:55 +0200, Jesper Dangaard Brouer wrote:
>> Make it possible to adjust the TCP default initial advertised receive
>> window, via sysctl /proc/sys/net/ipv4/tcp_init_recv_window.
>>
>> The window size is this value multiplied by the MSS of the connection.
>> The default value is (still) 10, as descibed in commit 356f039822b
>> (TCP: increase default initial receive window.)
>>
>> Allow minimum value of 1, but recommend against setting value below 2
>> in the documentation.
>>
>> Its possible to control/override this value per route table entry via
>> the iproute2 option initrwnd. Having the global default exported via
>> sysctl, helps determine the default setting, and make is easier to
>> adjust.
>
> I was wondering why its not symmetric :
>
> If we add a sysctl for initial receive window, we need another one for
> initial send window ?
Unlike the routing configuration, this is susceptible to serious abuse.
All it takes is for one jackass vendor to say that this should be set
to 1,000 in in sysctl.conf when using their product.
Whereas setting it on a per-route basis forces the person doing it
to actually consider that there might be ramifications that have to
do with the paths on which you are making this adjustment.
I would only let this in if you hard limited the setting to it's
current setting, 10. So people could decrease it.
next prev parent reply other threads:[~2012-09-21 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 8:55 [PATCH] tcp: sysctl for initial receive window Jesper Dangaard Brouer
2012-09-21 15:25 ` Eric Dumazet
2012-09-21 17:34 ` Jesper Dangaard Brouer
2012-09-21 17:56 ` David Miller [this message]
2012-09-21 18:32 ` Jesper Dangaard Brouer
2012-09-21 18:48 ` David Miller
2012-09-26 11:53 ` Eric Dumazet
2012-10-01 22:36 ` Yuchung Cheng
2012-09-25 5:29 ` Jan Engelhardt
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=20120921.135601.254379488076661898.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=nanditad@google.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;
as well as URLs for NNTP newsgroup(s).