Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Ananda Raju <Ananda.Raju@neterion.com>
Cc: netdev@vger.kernel.org, jgarzik@pobox.com,
	leonid.grossman@neterion.com, ravinandan.arakali@neterion.com,
	rapuru.sriram@neterion.com, ananda.raju@neterion.com,
	sivakumar.subramani@neterion.com
Subject: Re: [PATCH 2.6.17-rc5] support for TSO over IPv6.
Date: Mon, 5 Jun 2006 12:43:29 -0700	[thread overview]
Message-ID: <20060605124329.6e643ad3@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <Pine.GSO.4.10.10606051458530.20246-100000@guinness>

On Mon, 5 Jun 2006 15:09:45 -0400 (EDT)
Ananda Raju <Ananda.Raju@neterion.com> wrote:

> Hi,
> 	Neterion Xframe adapter supports TSO over IPv6 but the linux kernel 
> 	don't support TSO over Ipv6. This patch will allow TCP
> 	Segmentation Offload (TSO) packets to be created over IPv6. 
> 	
> 	The following table shows there is significant improvement in
> 	throughput with normal frames and CPU usage for both normal and jumbo.
> 
>         --------------------------------------------------
>         |          |     1500        |      9600         |
>         |          ------------------|-------------------|
>         |          | thru     CPU    |  thru     CPU     |
>         --------------------------------------------------
>         | TSO OFF  | 1.80   2.0% id  |  5.53   1.0% id   |
>         --------------------------------------------------
>         | TSO ON   | 2.61   74.0 id  |  5.52   32.0% id  |
>         --------------------------------------------------
> 
> Please review the patch.

There is one problem that may mean you have to rethink this.

You ignore the possible case of hardware that can do any kind of checksum
(ie. IP_F_HW_CSUM).  So I think you need to add a new flag NETIF_F_TSO6
for those types of devices, rather than overloading NETIF_F_TSO to mean
"can do TCP segmentation offload for IPV4 or IPV6".

Your proposal:
	ipv4 sum   : NETIF_F_IP_CSUM
	ipv6 sum   : NETIF_F_IP6_CSUM
	hw sum     : NETIF_F_HW_CSUM
	tso, ipv4  : NETIF_F_IP_CSUM + NETIF_F_TSO
	tso, ipv6  : NETIF_F_IP6_CSUM + NETIF_F_TSO

My proposal:
	ipv4 sum   : NETIF_F_IP_CSUM
	ipv6 sum   : NETIF_F_IP6_CSUM
	hw sum     : NETIF_F_HW_CSUM
	tso, ipv4  : NETIF_F_IP_CSUM + NETIF_F_TSO
	tso, ipv6  : NETIF_F_IP6_CSUM + NETIF_F_TSO6
	tso, hw    : NETIF_F_HW_CSUM + NETIF_F_TSO6


      reply	other threads:[~2006-06-05 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 19:09 [PATCH 2.6.17-rc5] support for TSO over IPv6 Ananda Raju
2006-06-05 19:43 ` Stephen Hemminger [this message]

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=20060605124329.6e643ad3@dxpl.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=Ananda.Raju@neterion.com \
    --cc=jgarzik@pobox.com \
    --cc=leonid.grossman@neterion.com \
    --cc=netdev@vger.kernel.org \
    --cc=rapuru.sriram@neterion.com \
    --cc=ravinandan.arakali@neterion.com \
    --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