Thread (9 messages) flat view 9 messages, 5 authors, 2012-10-01

Re: [PATCH] tcp: sysctl for initial receive window

From: David Miller <davem@davemloft.net>
Date: 2012-09-21 17:56:03

From: Eric Dumazet <redacted>
Date: Fri, 21 Sep 2012 17:25:11 +0200
On Fri, 2012-09-21 at 10:55 +0200, Jesper Dangaard Brouer wrote:
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help