From: "Michael Chan" <mchan@broadcom.com>
To: "Herbert Xu" <herbert@gondor.apana.org.au>
Cc: "Ananda Raju" <Ananda.Raju@neterion.com>,
netdev@vger.kernel.org, jgarzik@pobox.com, shemminger@osdl.org,
Leonid.Grossman@neterion.com, Ravinandan.Arakali@neterion.com,
sivakumar.subramani@neterion.com, Sriram.Rapuru@neterion.com
Subject: Re: [PATCH 2.6.17] support for TSO over IPv6
Date: Thu, 29 Jun 2006 19:06:51 -0700 [thread overview]
Message-ID: <1151633211.21798.25.camel@rh4> (raw)
In-Reply-To: <20060630003906.GA27200@gondor.apana.org.au>
On Fri, 2006-06-30 at 10:39 +1000, Herbert Xu wrote:
> BTW, does your card handle ECN correctly? If not then we should change
> the new ECN bit to apply to both TCPv4 and TCPv6 since
>
> 1) We now have a piece of hardware that handles TSO6 and it doesn't do ECN.
> 2) It's quite likely that if the NIC can handle ECN in TCPv4 then it can do
> it in TCPv6.
Don't we have a bigger problem if it doesn't support ECN with ipv6 TSO?
We either have to disable ECN when TSO is enabled like we used to for
ipv4, or provide the gso tcp segmentation for ipv6. Right?
next prev parent reply other threads:[~2006-06-30 2:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 22:18 [PATCH 2.6.17] support for TSO over IPv6 Ananda Raju
2006-06-29 22:30 ` David Miller
2006-06-29 23:32 ` Herbert Xu
2006-06-30 0:12 ` David Miller
2006-06-30 0:39 ` Herbert Xu
2006-06-30 2:06 ` Michael Chan [this message]
2006-06-30 2:11 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 20:46 Leonid Grossman
2006-07-01 3:38 ` Herbert Xu
2006-07-01 4:01 Leonid Grossman
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=1151633211.21798.25.camel@rh4 \
--to=mchan@broadcom.com \
--cc=Ananda.Raju@neterion.com \
--cc=Leonid.Grossman@neterion.com \
--cc=Ravinandan.Arakali@neterion.com \
--cc=Sriram.Rapuru@neterion.com \
--cc=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=sivakumar.subramani@neterion.com \
/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;
as well as URLs for NNTP newsgroup(s).