netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ravinandan Arakali" <ravinandan.arakali@neterion.com>
To: <netdev@vger.kernel.org>
Cc: <Steve.Whitaker@neterion.com>, <Mike.Doyle@neterion.com>,
	<Andrew.LaCroix@neterion.com>, <Ananda.Raju@neterion.com>,
	<dave.fenton@neterion.com>,
	"Leonid. Grossman \(E-mail\)" <leonid.grossman@neterion.com>
Subject: H/W requirements for NETIF_F_HW_CSUM
Date: Wed, 26 Jul 2006 10:28:00 -0700	[thread overview]
Message-ID: <006201c6b0d8$d831ba80$4510100a@pc.s2io.com> (raw)

Hello,
Our current NIC does not provide the actual checksum value on receive path.
Hence we only claim NETIF_F_IP_CSUM instead of the more general
NETIF_F_HW_CSUM.

To support this in a future adapter, we would like to know what exactly are
the requirements (on both Rx and Tx )to claim NETIF_F_HW_CSUM ?

Following are some specific questions:
1. On Tx, our adapter supports checksumming of TCP/UDP over IPv4 and IPv6.
This computation is TCP/UDP specific. Does the checksum calculation need to
be more generic ? Also, skbuff.h says that the checksum needs to be placed
at a specific location(skb->h.raw+skb->csum). I guess this means the adapter
needs to pass back the checksum to host driver after transmission. What
happens in case of TSO ?
2. On Rx, is it suffficient if we place the L4 checksum in skb->csum ? What
about L3 checksum ?

Thanks,
Ravi


             reply	other threads:[~2006-07-26 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 17:28 Ravinandan Arakali [this message]
2006-07-26 19:16 ` H/W requirements for NETIF_F_HW_CSUM Stephen Hemminger
2006-07-26 19:34   ` Ravinandan Arakali
2006-07-26 21:07     ` David Miller

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='006201c6b0d8$d831ba80$4510100a@pc.s2io.com' \
    --to=ravinandan.arakali@neterion.com \
    --cc=Ananda.Raju@neterion.com \
    --cc=Andrew.LaCroix@neterion.com \
    --cc=Mike.Doyle@neterion.com \
    --cc=Steve.Whitaker@neterion.com \
    --cc=dave.fenton@neterion.com \
    --cc=leonid.grossman@neterion.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).