> The problem is, with the default settings we are pretty safe
> about buffer overcommit. It also makes "I'm going to send you
> out of order
In 2.0.x I used 100% overcommit. With ethernet drivers doing
rx_copybreak that comes out about right in the wash. It was
originally a finger in air and gues exercise but it turned out near
enough right
Ok, right.
The issue is to get the max benefit of SACK with even moderately
latent paths we need to up it a bit, this is the crux of all the
complaints we are getting.
So my question is, can we up the default safely and if so by how much?
One thing you could do is compute the "average RAM in machine"
quantum at the time you made your settings for 2.0.x, and do the same
for now, and compute the interest compounded continuously. :-)
Later,
David S. Miller
davem@dm.cobaltmicro.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html