[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081107142950.13906925@lxorguk.ukuu.org.uk>
Date: Fri, 7 Nov 2008 14:29:50 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Dave Hudson <linux-kernel@...eteddy.net>
Cc: Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>,
Mikael Abrahamsson <swmike@....pp.se>,
David Miller <davem@...emloft.net>, daniel.blueman@...il.com,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>, linux-net@...r.kernel.org
Subject: Re: time for TCP ECN defaulting to on?
> Not all of the routers in question (the ones that crash, block packets
> or otherwise misbehave) are provided by ISPs
The ones that block and misbehave are the bigger problem. The ones that
crash are less of a problem and I think they are less common. Certainly
if they were common then people would be abusing the flaw routinely.
Similar end users tend to grasp "if it keeps crashing blame the supplier".
When stuff just mysteriously doesn't work it is a whole lot more
problematic. I think however Sally Floyd had it right and Alexey has it
wrong (as does Davem).
If you turn it off on a retransmit then you provide an immediate
incentive for everyone on the web server end of the business to fix their
network. Especially if you turn it off for second retransmit. That will
cause faulty ECN handling sites to feel "a bit slow" and we know from
marketing data that web site performance is crucial to customer base. A
three or four second delay getting a page up translates into dramatically
reduced hit counts.
Alan
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists