netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
To: "'David Miller'" <davem@davemloft.net>, <yoshfuji@linux-ipv6.org>
Cc: <herbert@gondor.apana.org.au>, <netdev@vger.kernel.org>
Subject: RE: [3/5] [NET]: Add software TSOv4
Date: Fri, 23 Jun 2006 17:28:12 -0700	[thread overview]
Message-ID: <004201c69725$14123700$4110100a@pc.s2io.com> (raw)
In-Reply-To: <20060622.143206.111203586.davem@davemloft.net>

Neterion's Xframe adapter supports TSO over IPv6.

Ravi

-----Original Message-----
From: netdev-owner@vger.kernel.org
[mailto:netdev-owner@vger.kernel.org]On Behalf Of David Miller
Sent: Thursday, June 22, 2006 2:32 PM
To: yoshfuji@linux-ipv6.org
Cc: herbert@gondor.apana.org.au; netdev@vger.kernel.org
Subject: Re: [3/5] [NET]: Add software TSOv4


From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Fri, 23 Jun 2006 00:04:03 +0900 (JST)

> In article <20060622081400.GC22671@gondor.apana.org.au> (at Thu, 22 Jun
2006 18:14:00 +1000), Herbert Xu <herbert@gondor.apana.org.au> says:
>
> > [NET]: Add software TSOv4
> >
> > This patch adds the GSO implementation for IPv4 TCP.
> >
> > Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> I'd appreciate if you code up IPv6 TCP as well. :-)

To my understanding doing IPV6 TCP TSO is a non-trivial task, even in
software.

The header editing is a lot more complicated because things like
routing and other extension headers can sit between IPV6 and TCP
header.

It is probably why IPV6 TSO hardware does not exist yet :)

Do not take this to mean I think it should not be implemented, I think
it should.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2006-06-24  0:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  8:12 [0/5] GSO: Generic Segmentation Offload Herbert Xu
2006-06-22  8:12 ` [1/5] [NET]: Merge TSO/UFO fields in sk_buff Herbert Xu
2006-06-22  8:13 ` [2/5] [NET]: Add generic segmentation offload Herbert Xu
2006-06-22  8:14 ` [3/5] [NET]: Add software TSOv4 Herbert Xu
2006-06-22  8:23   ` Herbert Xu
2006-06-22 15:04   ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-22 21:32     ` David Miller
2006-06-24  0:28       ` Ravinandan Arakali [this message]
2006-06-24  1:32         ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-26 18:33           ` Ravinandan Arakali
2006-06-23 19:33   ` Michael Chan
2006-06-23 21:26     ` Michael Chan
2006-06-23 23:38       ` Herbert Xu
2006-06-23 23:53         ` Herbert Xu
2006-06-24  3:08           ` Michael Chan
2006-06-26  6:55             ` David Miller
2006-06-22  8:14 ` [4/5] [NET]: Added GSO toggle Herbert Xu
2006-06-22  8:14 ` [5/5] [IPSEC]: Handle GSO packets Herbert Xu
2006-06-22  8:15 ` [0/5] GSO: Generic Segmentation Offload Herbert Xu
2006-06-22 10:08 ` David Miller
2006-06-22 14:28 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-24  5:36   ` Herbert Xu
  -- strict thread matches above, loose matches on Subject: below --
2006-06-20  9:09 Herbert Xu
2006-06-20  9:29 ` [3/5] [NET]: Add software TSOv4 Herbert Xu

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='004201c69725$14123700$4110100a@pc.s2io.com' \
    --to=ravinandan.arakali@neterion.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).