From: Pravin B Shelar <pshelar@nicira.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, jesse@nicira.com,
Pravin B Shelar <pshelar@nicira.com>
Subject: [PATCH v4 net-next 0/5] Tunneling: Tunnel restructuring.
Date: Mon, 25 Mar 2013 17:49:29 -0700 [thread overview]
Message-ID: <1364258969-3120-1-git-send-email-pshelar@nicira.com> (raw)
Following patch series restructure GRE and IPIP tunneling code
to make it modular. It adds ip_tunnel module which acts as
generic tunneling layer which has common code.
These patches do not change any functionality.
v3:v4:
- Fixed compilation error in ipv6.
- Few coding style fixes.
v2-v3:
- Use GPL exports for all export symbols.
- Set default config NET_IP_TUNNEL to m.
v1-v2:
- Dropped patch to convert gre_proto_lock to rtnl lock.
Pravin B Shelar (5):
GRE: Refactor GRE tunneling code.
IPIP: Use ip-tunneling code.
VXLAN: Fix vxlan stats handling.
VXLAN: Use IP Tunnels tunnel ENC encap API
Tunneling: use IP Tunnel stats APIs.
drivers/net/Kconfig | 1 +
drivers/net/vxlan.c | 100 +---
include/net/gre.h | 51 ++
include/net/ip6_tunnel.h | 1 +
include/net/ip_tunnels.h | 177 ++++++
include/net/ipip.h | 84 ---
net/ipv4/Kconfig | 7 +
net/ipv4/Makefile | 1 +
net/ipv4/af_inet.c | 1 -
net/ipv4/gre.c | 5 -
net/ipv4/ip_gre.c | 1504 ++++++++++------------------------------------
net/ipv4/ip_tunnel.c | 1035 +++++++++++++++++++++++++++++++
net/ipv4/ip_vti.c | 42 +--
net/ipv4/ipip.c | 748 ++---------------------
net/ipv4/ipmr.c | 2 +-
net/ipv6/Kconfig | 2 +
net/ipv6/af_inet6.c | 1 -
net/ipv6/ip6_gre.c | 45 +--
net/ipv6/ip6_tunnel.c | 1 +
net/ipv6/sit.c | 39 +--
20 files changed, 1668 insertions(+), 2179 deletions(-)
create mode 100644 include/net/ip_tunnels.h
delete mode 100644 include/net/ipip.h
create mode 100644 net/ipv4/ip_tunnel.c
next reply other threads:[~2013-03-26 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 0:49 Pravin B Shelar [this message]
2013-03-26 16:27 ` [PATCH v4 net-next 0/5] Tunneling: Tunnel restructuring 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=1364258969-3120-1-git-send-email-pshelar@nicira.com \
--to=pshelar@nicira.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.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).