From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
To: "'Michael Chan'" <mchan@broadcom.com>, <davem@davemloft.net>,
<herbert@gondor.apana.org.au>
Cc: <netdev@vger.kernel.org>
Subject: RE: [PATCH]NET: Add ECN support for TSO
Date: Fri, 7 Jul 2006 11:56:35 -0700 [thread overview]
Message-ID: <000f01c6a1f7$125ebaf0$4710100a@pc.s2io.com> (raw)
In-Reply-To: <1151464007.5124.13.camel@rh4>
Michael,
Are network cards expected to be aware-of and implement RFC3540(ECN with
nonces) ?
Thanks,
Ravi
-----Original Message-----
From: netdev-owner@vger.kernel.org
[mailto:netdev-owner@vger.kernel.org]On Behalf Of Michael Chan
Sent: Tuesday, June 27, 2006 8:07 PM
To: davem@davemloft.net; herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org
Subject: [PATCH]NET: Add ECN support for TSO
In the current TSO implementation, NETIF_F_TSO and ECN cannot be
turned on together in a TCP connection. The problem is that most
hardware that supports TSO does not handle CWR correctly if it is set
in the TSO packet. Correct handling requires CWR to be set in the
first packet only if it is set in the TSO header.
This patch adds the ability to turn on NETIF_F_TSO and ECN using
GSO if necessary to handle TSO packets with CWR set. Hardware
that handles CWR correctly can turn on NETIF_F_TSO_ECN in the dev->
features flag.
All TSO packets with CWR set will have the SKB_GSO_TCPV4_ECN set. If
the output device does not have the NETIF_F_TSO_ECN feature set, GSO
will split the packet up correctly with CWR only set in the first
segment.
It is further assumed that all hardware will handle ECE properly by
replicating the ECE flag in all segments. If that is not the case, a
simple extension of the logic will be required.
Signed-off-by: Michael Chan <mchan@broadcom.com>
next prev parent reply other threads:[~2006-07-07 18:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 3:06 [PATCH]NET: Add ECN support for TSO 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-07 20:57 Michael Chan
2006-07-07 21:59 ` David Miller
2006-07-07 22:52 ` David Miller
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-12 4:53 Michael Chan
2006-07-12 6:11 ` David Miller
2006-07-12 17:15 ` Ravinandan Arakali
2006-07-13 19:35 Michael Chan
2006-07-14 5:03 ` David Miller
2006-07-14 16:12 Dan Reader
2006-07-26 19:40 ` Michael Chan
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='000f01c6a1f7$125ebaf0$4710100a@pc.s2io.com' \
--to=ravinandan.arakali@neterion.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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;
as well as URLs for NNTP newsgroup(s).