dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Hall <mhall-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
To: Thomas Monjalon
	<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: IPv6 Offload Capabilities
Date: Mon, 5 Jan 2015 21:30:27 -0800	[thread overview]
Message-ID: <20150106053027.GC17455@mhcomputing.net> (raw)
In-Reply-To: <20150106052537.GB17455-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>

On Mon, Jan 05, 2015 at 09:25:37PM -0800, Matthew Hall wrote:
> The same computation algorithm must be reused to calculate the IPV6 
> Pseudoheader checksum when generating ICMPV6, UDPV6, and other L4 protocols 
> whose definitions were retroactively modified to include the IPV6 
> pseudoheader, that happen to use the same checksum in L4 which IP used in L3.

To clarify, this is the part of the RFC which mentions it:

https://tools.ietf.org/html/rfc2460#section-8.1

Also, somebody else mentioned using TSO (TCP Segmentation Offload).

I did look at it but since it only seemed to work in TCP if I read everything 
right, that'd mean I had inconsistent code for IPv4 versus IPv6 stack, and 
inconsistent behavior for TCP from that for ICMP and UDP.

I was trying to avoid writing too much of this messy code if possible.

Matthew.

  parent reply	other threads:[~2015-01-06  5:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05  7:56 IPv6 Offload Capabilities Gal Sagie
     [not found] ` <CAG9LJa6qY=LeiN+sPQGx7ok-RWwf9uXm_Vz4-2NLTW8XvGoU5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-05  8:09   ` Matthew Hall
     [not found]     ` <C6595EEB-8329-49F9-9745-52887AE9F848-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2015-01-05  8:36       ` Thomas Monjalon
2015-01-06  5:25         ` Matthew Hall
     [not found]           ` <20150106052537.GB17455-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2015-01-06  5:30             ` Matthew Hall [this message]
2015-01-14 11:29             ` Thomas Monjalon
2015-01-05  8:33   ` Olivier MATZ

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=20150106053027.GC17455@mhcomputing.net \
    --to=mhall-hv3ognyu3jfzzajbqzqcxq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.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).