From: Tom Herbert <tom@herbertland.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <kernel-team@fb.com>
Subject: [PATCH next-next 0/7] net: Cleanup IPv6 ip tunnels
Date: Fri, 29 Apr 2016 17:12:14 -0700 [thread overview]
Message-ID: <1461975141-954269-1-git-send-email-tom@herbertland.com> (raw)
The IPv6 tunnel code is very different from IPv4 code. There is a lot
of redundancy with the IPv4 code, particularly in the GRE tunneling.
This patch set cleans up the tunnel code to make the IPv6 code look
more like the IPv4 code and use common functions between the two
stacks where possible.
This work should make it easier to maintain and extend the IPv6 ip
tunnels.
Items in this patch set:
- Cleanup IPv6 tunnel receive path (ip6_tnl_rcv). Includes using
gro_cells and exporting ip6_tnl_rcv so the ip6_gre can call it
- Move GRE functions to common header file (tx functions) or
gre_demux.c (rx functions like gre_parse_header)
- Call common GRE functions from IPv6 GRE
- Create ip6_tnl_xmit (to be like ip_tunnel_xmit)
Tested:
Ran super_netperf tests for TCP_RR and TCP_STREAM for:
- IPv4 over gre, gretap, gre6, gre6tap
- IPv6 over gre, gretap, gre6, gre6tap
- ipip
- ip6ip6
- ipip/gue
- IPv6 over gre/gue
- IPv4 over gre/gue
Tom Herbert (7):
ipv6: Cleanup IPv6 tunnel receive path
gre: Move utility functions to common headers
gre6: Cleanup GREv6 receive path, call common GRE functions
ipv6: Create ip6_tnl_xmit
gre: Create common functions for transmit
ipv6: Generic tunnel cleanup
gre6: Cleanup GREv6 transmit path, call common GRE functions
include/net/gre.h | 104 +++++++++++++
include/net/ip6_tunnel.h | 11 +-
net/ipv4/gre_demux.c | 64 ++++++++
net/ipv4/ip_gre.c | 199 +++---------------------
net/ipv6/ip6_gre.c | 392 +++++++++--------------------------------------
net/ipv6/ip6_tunnel.c | 266 +++++++++++++++++++++-----------
6 files changed, 452 insertions(+), 584 deletions(-)
--
2.8.0.rc2
next reply other threads:[~2016-04-30 0:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 0:12 Tom Herbert [this message]
2016-04-30 0:12 ` [PATCH next-next 1/7] ipv6: Cleanup IPv6 tunnel receive path Tom Herbert
2016-04-30 0:12 ` [PATCH next-next 2/7] gre: Move utility functions to common headers Tom Herbert
2016-05-03 11:29 ` Jiri Benc
2016-05-04 4:53 ` David Miller
2016-05-04 8:35 ` Jiri Benc
2016-05-04 16:45 ` David Miller
2016-04-30 0:12 ` [PATCH next-next 3/7] gre6: Cleanup GREv6 receive path, call common GRE functions Tom Herbert
2016-04-30 0:12 ` [PATCH next-next 4/7] ipv6: Create ip6_tnl_xmit Tom Herbert
2016-04-30 0:12 ` [PATCH next-next 5/7] gre: Create common functions for transmit Tom Herbert
2016-04-30 0:12 ` [PATCH net-next 6/7] ipv6: Generic tunnel cleanup Tom Herbert
2016-04-30 0:12 ` [PATCH next-next 7/7] gre6: Cleanup GREv6 transmit path, call common GRE functions Tom Herbert
2016-04-30 1:00 ` [PATCH next-next 0/7] net: Cleanup IPv6 ip tunnels Alexander Duyck
2016-05-02 19:32 ` Tom Herbert
2016-05-02 19:42 ` Alexander Duyck
2016-05-02 23:23 ` David Miller
2016-05-03 2:03 ` Alexander Duyck
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=1461975141-954269-1-git-send-email-tom@herbertland.com \
--to=tom@herbertland.com \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--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).