public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel J Blueman" <daniel.blueman@gmail.com>
To: "Mikael Abrahamsson" <swmike@swm.pp.se>,
	"David Miller" <davem@davemloft.net>,
	LKML <linux-kernel@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>,
	linux-net@vger.kernel.org,
	"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Subject: Re: time for TCP ECN defaulting to on?
Date: Fri, 7 Nov 2008 13:43:40 +0000	[thread overview]
Message-ID: <6278d2220811070543p51ca2139t13aba28e6dba5ff4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0811071341430.23792@wrl-59.cs.helsinki.fi>

On Fri, Nov 7, 2008 at 12:22 PM, Ilpo Järvinen
<ilpo.jarvinen@helsinki.fi> wrote:
> On Fri, 7 Nov 2008, Mikael Abrahamsson wrote:
>> On Fri, 7 Nov 2008, Ilpo Järvinen wrote:
>> > I think you partially miss the point here. In many cases not every
>> > single
>> > router has to _support_ ECN to get its benefits, not-supporting is not
>> > the
>> > problem in itself (though it would be nice to get that "fixed" as well)
>> > but
>> > breaking ecn-enabled connections. I suppose you didn't check that
>> > aspect?
>> > I'd guess those mentioned devices will interoperate just fine since one
>> > can
>> > mostly connect ok with ecn too besides rare exceptions rather than
>> > things
>> > being vice-versa.
>>
>> I don't understand. My point is that most of the ISP core equipment out
>> there
>> doesn't act on ECN rendering it mostly useless. The N in ECN renders
>> useless
>> because there is no device doing the *notification*. They'll just pass the
>> traffic without acting on it differently regardless if ECN is on or off.

I've been running with ECN enabled on all my client linux systems and
(personal) webservers for the past 6 or so years. When I've
encountered issues accessing particular hosts, I turn it and TCP
window scaling off, but invariably it is always another cause.

If most ECN-broken hardware is embedded consumer appliances (which are
generally short-lifespan and moving more and more to linux), then we
avoid hurting these users by enabling ECN per default when eg
CONFIG_IP_ADVANCED_ROUTER is set (to little direct benefit of course).
It's a start and a constructive idea; by doing this and documenting
it, we provide a wake-up call for vendors, laying the path for
enabling it for all types of host in a few years. Even enabling ECN
for -rc kernels will raise awareness.

Alternatively, an ECN-day could be publicised targeting the linux tech
community, where we can report failing networks/sites to a central
website to quantify actual potential negative impact.

But doing nothing is cyclic - when will the natural break suddenly occur?
-- 
Daniel J Blueman

  reply	other threads:[~2008-11-07 13:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 14:32 time for TCP ECN defaulting to on? Daniel J Blueman
2008-11-04 16:16 ` Dave Hudson
2008-11-04 22:52   ` David Miller
2008-11-05  1:16     ` Michael Chan
2008-11-05  5:58       ` David Miller
2008-11-05  6:31         ` Michael Chan
2008-11-05  7:29           ` David Miller
2008-11-16  9:13     ` Herbert Xu
2008-11-16  9:24       ` David Miller
2008-11-05 22:20 ` Mikael Abrahamsson
2008-11-05 23:10   ` David Miller
2008-11-07  4:46     ` Mikael Abrahamsson
2008-11-07  4:49       ` David Miller
2008-11-07  7:53       ` Ilpo Järvinen
2008-11-07  8:11         ` Mikael Abrahamsson
2008-11-07  9:12           ` Bjørn Mork
2008-11-07 11:16             ` Mikael Abrahamsson
2008-11-07 11:28           ` Ilpo Järvinen
2008-11-07 11:38             ` Mikael Abrahamsson
2008-11-07 12:22               ` Ilpo Järvinen
2008-11-07 13:43                 ` Daniel J Blueman [this message]
2008-11-07 14:30                   ` Ilpo Järvinen
2008-11-07 11:18         ` Dave Hudson
2008-11-07 14:29           ` Alan Cox
2008-11-07 14:45             ` David Newall
2008-11-07 15:07               ` Rémi Denis-Courmont
2008-11-07 18:38               ` John Heffner
2008-11-07 14:33           ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6278d2220811070543p51ca2139t13aba28e6dba5ff4@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox