netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Duyck <aduyck@mirantis.com>
To: jesse@kernel.org, netdev@vger.kernel.org, davem@davemloft.net,
	alexander.duyck@gmail.com, tom@herbertland.com
Subject: [net-next PATCH 0/5] Add support for offloads with IPv6 GRE tunnels
Date: Thu, 14 Apr 2016 15:33:30 -0400	[thread overview]
Message-ID: <20160414192709.12934.82858.stgit@ahduyck-xeon-server> (raw)

This patch series enables the use of segmentation and checksum offloads
with IPv6 based GRE tunnels.

In order to enable this series I had to make a change to
iptunnel_handle_offloads so that it would no longer free the skb.  This was
necessary as there were multiple paths in the IPv6 GRE code that required
the skb to still be present so it could be freed.  As it turned out I
believe this actually fixes a bug that was present in FOU/GUE based tunnels
anyway.

Below is a quick breakdown of the performance gains seen with a simple
netperf test passing traffic through a ip6gretap tunnel and then an i40e
interface:

Throughput Throughput  Local Local   Result 
           Units       CPU   Service Tag    
                       Util  Demand         
                       %  
3544.93    10^6bits/s  6.30  4.656   "before"
13081.75   10^6bits/s  3.75  0.752   "after"

---

Alexander Duyck (5):
      ip_tunnel_core: iptunnel_handle_offloads returns int and doesn't free skb
      ip6gretap: Fix MTU to allow for Ethernet header
      ip6gre: Add support for basic offloads offloads excluding GSO
      GRE: Add support for GRO/GSO of IPv6 GRE traffic
      ip6gre: Add support for GSO


 drivers/net/geneve.c            |   32 ++++++---------
 drivers/net/vxlan.c             |    6 +--
 include/net/ip_tunnels.h        |    2 -
 include/net/udp_tunnel.h        |    3 -
 net/ipv4/fou.c                  |   16 ++++----
 net/ipv4/gre_offload.c          |   14 ++++++-
 net/ipv4/ip_gre.c               |   20 +++-------
 net/ipv4/ip_tunnel_core.c       |   13 ++----
 net/ipv4/ipip.c                 |    7 +--
 net/ipv6/ip6_gre.c              |   81 +++++++++++++++++++++++++++------------
 net/ipv6/sit.c                  |   14 +++----
 net/netfilter/ipvs/ip_vs_xmit.c |    6 +--
 12 files changed, 116 insertions(+), 98 deletions(-)

             reply	other threads:[~2016-04-14 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 19:33 Alexander Duyck [this message]
2016-04-14 19:33 ` [net-next PATCH 1/5] ip_tunnel_core: iptunnel_handle_offloads returns int and doesn't free skb Alexander Duyck
2016-04-14 19:33 ` [net-next PATCH 2/5] ip6gretap: Fix MTU to allow for Ethernet header Alexander Duyck
2016-04-14 19:33 ` [net-next PATCH 3/5] ip6gre: Add support for basic offloads offloads excluding GSO Alexander Duyck
2016-04-14 19:33 ` [net-next PATCH 4/5] GRE: Add support for GRO/GSO of IPv6 GRE traffic Alexander Duyck
2016-04-14 19:34 ` [net-next PATCH 5/5] ip6gre: Add support for GSO Alexander Duyck
2016-04-16 23:12 ` [net-next PATCH 0/5] Add support for offloads with IPv6 GRE tunnels 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=20160414192709.12934.82858.stgit@ahduyck-xeon-server \
    --to=aduyck@mirantis.com \
    --cc=alexander.duyck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jesse@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tom@herbertland.com \
    /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).