[lkml]   [2008]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: time for TCP ECN defaulting to on?
On Fri, 7 Nov 2008, Mikael Abrahamsson wrote:

> On Wed, 5 Nov 2008, David Miller wrote:
> > This kind of thinking just perpetuates the problem forever.
> It's like the TCP option order "bug", where some devices would drop the
> packets because of buggy implementations, that was changed in Linux to work
> around others buggy code, and I see "ECN blackhole detection" as a similar
> measure.

That is entirely bogus claim! The different ordering of options cost us
nothing, while disabling ECN certainly has an innumerable cost both in
performance and in nobody taking the initiative which makes the situation
worse for everybody.

And about somebody earlier claiming that they'll get an impressions that
Linux stack is broken (if such people even know that there's some network
stack in Linux :-))... I'm rather sure those isp supports etc. put a blaim
on us anyway even when loads of counterproof would exists because it's
just cheaper to do nothing and blaim linux instead. Also some claims
asserted by incompetent people easily start to live among random forums;
an example from the previous incident: "since disabling timestamps helps,
it must be that timestamps are broken" (and somebody even "more clueful"
added that they got enabled for 2.6.27?!?), needless to say, neither


 \ /
  Last update: 2008-11-07 08:55    [W:0.099 / U:0.188 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site