netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: netdev@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
	"David S. Miller" <davem@davemloft.net>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [NET] IOC3: Switch hw checksumming to ethtool configurable.
Date: Mon, 30 Jul 2007 16:06:54 -0400	[thread overview]
Message-ID: <46AE44DE.8000107@garzik.org> (raw)
In-Reply-To: <20070725113157.GA29416@linux-mips.org>

Ralf Baechle wrote:
> Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

applied to #upstream (2.6.24)


> I've previously sent out this patch a long time ago.  At that time I was
> told NETIF_F_IP_CSUM wouldn't make any sense without NETIF_F_SG.  IOC3's
> S/G abilities are very limited; it can do upto three segments of which
> the first one is upto 104 bytes and part of the packet's TX ring entry,
> the second and 3rd ones can be anywhere in the 64-bit PCI address space
> but may not cross a 16kB page boundary.  So setting NETIF_F_SG isn't
> really an option unless the IOC3 was going to linearize any packet it
> can't cope with itself.
> 
> So the big question, does NETIF_F_IP_CSUM without NETIF_F_SG make sense?

Conventional wisdom has always been that NETIF_F_SG is required if 
NETIF_F_*CSUM is present, and vice versa.

I admit I've not verified this in the past year or two.

	Jeff



      reply	other threads:[~2007-07-30 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 11:31 [NET] IOC3: Switch hw checksumming to ethtool configurable Ralf Baechle
2007-07-30 20:06 ` Jeff Garzik [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=46AE44DE.8000107@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.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).