netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ecree@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com,
	tom@herbertland.net
Subject: Re: [PATCH v5 net-next 0/8] Local Checksum Offload
Date: Fri, 12 Feb 2016 05:53:12 -0500 (EST)	[thread overview]
Message-ID: <20160212.055312.319096573102657816.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1602112024140.14893@ec-desktop.uk.level5networks.com>

From: Edward Cree <ecree@solarflare.com>
Date: Thu, 11 Feb 2016 20:46:00 +0000

> Re-tested VxLAN; everything else is unchanged from v4.
> 
> Changes from v4:
>  * Rebased series to fix conflicts with vxlan/vxlan6 merge.
> 
> Changes from v3:
>  * Fixed inverted checksum values introduced in v3.
>  * Don't mangle zero checksums in GRE.
>  * Clear skb->encapsulation in iptunnel_handle_offloads when not using
>    CHECKSUM_PARTIAL, lest drivers incorrectly interpret that as a request
>    for inner checksum offload.
> 
> Changes from v2:
>  * Added support for IPv4 GRE.
>  * Split out 'always set up for checksum offload' into its own patch.
>  * Removed csum_help from iptunnel_handle_offloads.
>  * Rewrote LCO callers to only fold once.
>  * Simplified nocheck handling.
> 
> Changes from v1:
>  * Enabled support in more encapsulation protocols.
>    I think it now covers everything except GRE.
>  * Wrote up some documentation covering TX checksum offload, LCO and RCO.

Series applied, thanks Edward.

      reply	other threads:[~2016-02-12 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 20:46 [PATCH v5 net-next 0/8] Local Checksum Offload Edward Cree
2016-02-12 10:53 ` David Miller [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=20160212.055312.319096573102657816.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=linux-net-drivers@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=tom@herbertland.net \
    /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).