tcp: restore correct limit
authorEric Dumazet <eric.dumazet@gmail.com>
Tue, 10 Apr 2012 00:56:42 +0000 (00:56 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 27 Apr 2012 17:17:01 +0000 (10:17 -0700)
commitce30c9603e01ed68e7536a0936f30ec047acd57f
treee02a59a7a5f3360142d6c5eefb9fc5bedf45f92a
parent44ffc7c1c604e0ea5dd727b440b74b6121d152d9
tcp: restore correct limit

[ Upstream commit 5fb84b1428b271f8767e0eb3fcd7231896edfaa4 ]

Commit c43b874d5d714f (tcp: properly initialize tcp memory limits) tried
to fix a regression added in commits 4acb4190 & 3dc43e3,
but still get it wrong.

Result is machines with low amount of memory have too small tcp_rmem[2]
value and slow tcp receives : Per socket limit being 1/1024 of memory
instead of 1/128 in old kernels, so rcv window is capped to small
values.

Fix this to match comment and previous behavior.

Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Glauber Costa <glommer@parallels.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
net/ipv4/tcp.c