Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753381AbYKGHxf (ORCPT ); Fri, 7 Nov 2008 02:53:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751121AbYKGHxV (ORCPT ); Fri, 7 Nov 2008 02:53:21 -0500 Received: from courier.cs.helsinki.fi ([128.214.9.1]:44058 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751007AbYKGHxU (ORCPT ); Fri, 7 Nov 2008 02:53:20 -0500 Date: Fri, 7 Nov 2008 09:53:18 +0200 (EET) From: "=?ISO-8859-1?Q?Ilpo_J=E4rvinen?=" X-X-Sender: ijjarvin@wrl-59.cs.helsinki.fi To: Mikael Abrahamsson cc: David Miller , daniel.blueman@gmail.com, LKML , Netdev , linux-net@vger.kernel.org Subject: Re: time for TCP ECN defaulting to on? In-Reply-To: Message-ID: References: <6278d2220811040632u7a36d68ekad5de517fd0671bb@mail.gmail.com> <20081105.151015.206163697.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1564 Lines: 35 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 holds. -- i. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/