Re: RFC: Nagle latency tuning

[Andi Kleen <andi@firstfloor.org>]

> There are many cases where perfectly acceptible heuristics

For very low values of "perfect" :)

> don't perform optimally, this doesn't mean we disable them
> by default.

Well they're just broken on a larger and larger fraction
of the internet.  Router technology more and more often
knows something about ports these days and handles flows
differently. Assuming they do not is more and more 
wrong. It's one of these things which looks cool on first
look but when you dig deeper is just a bad idea.

How should we call a heuristics that is often
wrong. A "wrongistic"?  :)

> > NAT.
> 
> I am more than aware of this, however this doesn't mean it is
> sane 

I agree with you that they're not sane, but they should still 
be supported. Technically at least they don't violate any standards
afaik.

Linux should work well even with such setups. In fact it has
no other choice because they're so common. "Be liberal
what you accept, be conservative what you send". This violates
the second principle.

> and this kind of setup makes many useful internet services
> inaccessible.

Sure, in fact that's usually why they were done in the first place,
but Linux shouldn't make it unnecessarily worse.

Anyways enough said. I guess we have to agree to disagree on
this. For completeness I'll still send the patch to set the sysctl
by default though just in case you reconsider.

-Andi

-- 
ak@linux.intel.com