Re: RFC: Nagle latency tuning

[Andi Kleen <andi@firstfloor.org>]

> It is not an invalid estimate even in the NAT case, 

Typical case: you got a large company network behind a NAT.
First user has a very crappy wireless connection behind a slow
intercontinental link talking to the outgoing NAT router. He connectes to 
your internet server first and the window, slow start etc. parameters 
for him are saved in the dst_entry.  

The next guy behind the same NAT is in the same building
as the router who connects the company to the internet. He
has a much faster line. He connects to the same server. 
They will share the same dst and inetpeer entries.

The parameters saved earlier for the same IP are clearly invalid
for the second case. The link characteristics are completely 
different.

Also did you know there are there are whole countries behind
NAT. e.g. I was told that all of Saudi Arabia only comes from
a small handfull of IP addresses. It would surprise me if 
all of KSA has the same link characteristics? @)

Ah I see there's a sysctl now to disable this. How about
setting it by default?

-Andi