From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: ravinandan.arakali@neterion.com, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, steve.arden@neterion.com,
Dan.Reader@neterion.com, leonid.grossman@neterion.com,
ananda.raju@neterion.com
Subject: Re: [PATCH]NET: Add ECN support for TSO
Date: Thu, 13 Jul 2006 22:03:30 -0700 (PDT) [thread overview]
Message-ID: <20060713.220330.118526029.davem@davemloft.net> (raw)
In-Reply-To: <1551EAE59135BE47B544934E30FC4FC093F9C3@NT-IRVA-0751.brcm.ad.broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Thu, 13 Jul 2006 12:35:37 -0700
> When RFC3540 is implemented, the stack will randomly use ECT(0) or
> ECT(1) on the TSO super segments. On each of these super segments,
> the hardware will replicate the ECT code point. This will keep
> everything stateless. The stack only needs to know the TSO factor
> (number of divided segements) for each TSO super segement to keep
> track of the NS.
Correct, and this is all transparent to the device as long
as it replicates the ECT bit in every sub-frame.
The only real issues are on receive for LRO where the parity
of NS needs to be maintained.
next prev parent reply other threads:[~2006-07-14 5:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 19:35 [PATCH]NET: Add ECN support for TSO Michael Chan
2006-07-14 5:03 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-14 16:12 Dan Reader
2006-07-26 19:40 ` Michael Chan
2006-07-12 4:53 Michael Chan
2006-07-12 6:11 ` David Miller
2006-07-12 17:15 ` Ravinandan Arakali
2006-07-08 1:01 Michael Chan
2006-07-08 20:32 ` David Miller
2006-07-12 1:45 ` Ravinandan Arakali
2006-07-12 1:51 ` David Miller
2006-07-13 17:26 ` Ravinandan Arakali
2006-07-07 20:57 Michael Chan
2006-07-07 21:59 ` David Miller
2006-07-07 22:52 ` David Miller
2006-06-28 3:06 Michael Chan
2006-06-28 3:10 ` Herbert Xu
2006-06-28 3:40 ` Michael Chan
2006-06-28 3:48 ` Herbert Xu
2006-06-28 4:37 ` Michael Chan
2006-06-28 4:42 ` Herbert Xu
2006-06-28 4:54 ` Michael Chan
2006-06-28 4:57 ` Herbert Xu
2006-06-29 19:30 ` David Miller
2006-07-07 18:56 ` Ravinandan Arakali
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=20060713.220330.118526029.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Dan.Reader@neterion.com \
--cc=ananda.raju@neterion.com \
--cc=herbert@gondor.apana.org.au \
--cc=leonid.grossman@neterion.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=ravinandan.arakali@neterion.com \
--cc=steve.arden@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).