From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: linux-kernel@blueteddy.net, 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: Tue, 04 Nov 2008 21:58:39 -0800 (PST) [thread overview]
Message-ID: <20081104.215839.132524253.davem@davemloft.net> (raw)
In-Reply-To: <1225847763.11369.43.camel@HP1>
From: "Michael Chan" <mchan@broadcom.com>
Date: Tue, 04 Nov 2008 17:16:03 -0800
> 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.
Hmm, good point, but if that is what happens I don't know if I agree
with it.
If "take care of ECN" means doing TSO in software, that's in my
opinion the wrong thing to do.
next prev parent reply other threads:[~2008-11-05 5:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 14:32 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 [this message]
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 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=20081104.215839.132524253.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@blueteddy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mchan@broadcom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®