From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: herbert@gondor.apana.org.au
Cc: jeff@garzik.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org
Subject: Re: [RFC/PATCH] SO_NO_CHECK for IPv6
Date: Thu, 22 Nov 2007 11:46:21 +0900 (JST) [thread overview]
Message-ID: <20071122.114621.02788123.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20071122023403.GA3409@gondor.apana.org.au>
In article <20071122023403.GA3409@gondor.apana.org.au> (at Thu, 22 Nov 2007 10:34:03 +0800), Herbert Xu <herbert@gondor.apana.org.au> says:
> On Wed, Nov 21, 2007 at 07:17:40PM -0500, Jeff Garzik wrote:
> >
> > For those interested, I am dealing with a UDP app that already does very
> > strong checksumming and encryption, so additional software checksumming
> > at the lower layers is quite simply a waste of CPU cycles. Hardware
> > checksumming is fine, as long as its "free."
>
> No matter how strong your underlying checksumming is it's not
> going to protect the IPv6 header is it :)
In that sense, we should use AH.
--yoshfuji
next prev parent reply other threads:[~2007-11-22 2:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 12:45 [RFC/PATCH] SO_NO_CHECK for IPv6 Jeff Garzik
2007-11-21 13:20 ` YOSHIFUJI Hideaki / 吉藤英明
2007-11-21 13:42 ` Herbert Xu
2007-11-22 0:17 ` Jeff Garzik
2007-11-22 2:34 ` Herbert Xu
2007-11-22 2:46 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2007-11-23 1:13 ` David Miller
2007-11-23 6:06 ` David Schwartz
2007-11-24 6:00 ` Herbert Xu
2007-11-25 15:41 ` David Schwartz
2007-11-26 2:47 ` Herbert Xu
2007-11-21 18:35 ` 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=20071122.114621.02788123.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--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).