From: "Michael Chan" <mchan@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: "linux-kernel@blueteddy.net" <linux-kernel@blueteddy.net>,
"daniel.blueman@gmail.com" <daniel.blueman@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-net@vger.kernel.org" <linux-net@vger.kernel.org>
Subject: Re: time for TCP ECN defaulting to on?
Date: Tue, 04 Nov 2008 17:16:03 -0800 [thread overview]
Message-ID: <1225847763.11369.43.camel@HP1> (raw)
In-Reply-To: <20081104.145242.112948002.davem@davemloft.net>
On Tue, 2008-11-04 at 14:52 -0800, David Miller wrote:
> From: Dave Hudson <linux-kernel@blueteddy.net>
> Date: Tue, 04 Nov 2008 16:16:03 +0000
>
> > Daniel J Blueman wrote:
> > > Is it time to enable TCP ECN per default and get the benefits, since
> > > router support has been around and known-about for really considerable
> > > time?
> > > Perhaps it should be a question of enabling it, and educating people
> > > to disable it if they run into issues, since we'll probably be in the
> > > same situation in 5 years...and it'll be some time before these
> > > kernels hit devices/servers anyway.
> > > Daniel
> >
> > Unfortunately I think you'll find there are sufficiently large
> > numbers of broken SOHO routers out there that if you try this you'll
> > cause a lot of problems. The problems range from no connectivity to
> > in a few extreme cases routers actually crashing or behaving in very
> > unpredictable ways. Here's one summary that got presented to the
> > IETF about 18 months ago:
> >
> > http://www.ietf.org/proceedings/07mar/slides/tsvarea-3/sld6.htm
>
> Another issue is that, even if we turn it on by default, it won't
> be on for a significant number of network cards out there.
>
> This is because TSO, which is on by default, doesn't support ECN
> in many implementations.
I think this is no longer a limitation. The GSO code will take care of
ECN properly if the hardware does not support it when doing TSO.
next prev parent reply other threads:[~2008-11-05 1:18 UTC|newest]
Thread overview: 29+ 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 [this message]
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
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=1225847763.11369.43.camel@HP1 \
--to=mchan@broadcom.com \
--cc=daniel.blueman@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@blueteddy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.