[TCP]: slow_start_after_idle should influence cwnd validation too
authorDavid S. Miller <davem@sunset.davemloft.net>
Mon, 9 Apr 2007 20:23:14 +0000 (13:23 -0700)
committerDavid S. Miller <davem@sunset.davemloft.net>
Mon, 9 Apr 2007 20:31:15 +0000 (13:31 -0700)
commit15d33c070ddde99f7368e6b17b71d22c866f97d9
tree00e779b01fb3c48e61b3ccc4de8f082e1b929cc4
parent699784b7614ce61b16a075445b8e5b6c379c5086
[TCP]: slow_start_after_idle should influence cwnd validation too

For the cases that slow_start_after_idle are meant to deal
with, it is almost a certainty that the congestion window
tests will think the connection is application limited and
we'll thus decrease the cwnd there too.  This defeats the
whole point of setting slow_start_after_idle to zero.

So test it there too.

We do not cancel out the entire tcp_cwnd_validate() function
so that if the sysctl is changed we still have the validation
state maintained.

Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp_output.c