From: David Miller <davem@davemloft.net>
To: swmike@swm.pp.se
Cc: daniel.blueman@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: time for TCP ECN defaulting to on?
Date: Wed, 05 Nov 2008 15:10:15 -0800 (PST) [thread overview]
Message-ID: <20081105.151015.206163697.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0811052316210.10993@uplift.swm.pp.se>
From: Mikael Abrahamsson <swmike@swm.pp.se>
Date: Wed, 5 Nov 2008 23:20:25 +0100 (CET)
> So the upside of enabling it is minimal (I'd gladly see data proving
> the opposite) and the downside is a lot of trouble with lots of
> older devices which behave badly when ECN is enabled.
This kind of thinking just perpetuates the problem forever.
If nothing important on end nodes enables it by default, people
running core routers have no reason to turn it on, and so on and so
forth.
Linux is much bigger and smarter than that, so we should break
the loop and enable it by default some point soon.
next prev parent reply other threads:[~2008-11-05 23:10 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 [this message]
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
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=20081105.151015.206163697.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel.blueman@gmail.com \
--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