maybe, but if that's the case, then there are a lot of broken gateways
or filters out there... is it really healthy to make tcp_dsack on by
default? I know it was meant to be backward compatible but it doesn't
look like it turned out that way; seems like it'd be more of an
optimization than a default.
On Oct 22, 2008, at 11:11 AM, Bastian Blank wrote:
On Tue, Oct 21, 2008 at 04:09:43PM -0400, Jonathan Zdziarski wrote:
causes the web page to hang every other query. disabling
net.ipv4.tcp_dsack
seems to resolve the problem, leaving me to believe something might
be wrong
in how linux handles dupe sacks.
Show dumps. Usualy such problems are caused by broken gateways or
filters.
Bastian
--
What kind of love is that? Not to be loved; never to have shown love.
-- Commissioner Nancy Hedford, "Metamorphosis",
stardate 3219.8
Jonathan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
