From: Jiri Benc <jbenc@redhat.com>
To: netdev@vger.kernel.org
Subject: [PATCH net-next 0/5] vxlan: implement Generic Protocol Extension (GPE)
Date: Fri, 26 Feb 2016 08:48:36 +0100 [thread overview]
Message-ID: <cover.1456472746.git.jbenc@redhat.com> (raw)
VXLAN-GPE can operate in two modes: with encapsulated Ethernet header
(L2 mode) or with L3 header (e.g. IP header) directly following VXLAN-GPE
header (L3 mode).
Add support for both modes. The L2 mode is simple, as it's basically the
same as plain VXLAN, only with added bits in the header. The L3 mode is more
complicated. The patches adding it follow the same model as the tun/tap
driver: depending on the chosen mode, the vxlan interface is created either
as ARPHRD_ETHER (L2 mode) or ARPHRD_NONE (L3 mode).
Note that the internal fdb control plane cannot be used together with
VXLAN-GPE and attempt to configure it will be rejected by the driver. This
in theory could be relaxed for L2 mode in the future if such need arises.
Jiri Benc (5):
vxlan: implement GPE in L2 mode
vxlan: move L2 mode initialization to a separate function
vxlan: move fdb code to common location in vxlan_xmit
vxlan: fix too large pskb_may_pull with remote checksum
vxlan: implement GPE in L3 mode
drivers/net/vxlan.c | 223 ++++++++++++++++++++++++++++++++++++-------
include/net/vxlan.h | 63 +++++++++++-
include/uapi/linux/if_link.h | 9 ++
3 files changed, 258 insertions(+), 37 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-02-26 7:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 7:48 Jiri Benc [this message]
2016-02-26 7:48 ` [PATCH net-next 1/5] vxlan: implement GPE in L2 mode Jiri Benc
2016-02-26 23:51 ` Tom Herbert
2016-02-27 19:31 ` Jiri Benc
2016-02-27 20:54 ` Tom Herbert
2016-02-27 21:02 ` Tom Herbert
2016-02-29 10:23 ` Jiri Benc
2016-02-29 17:13 ` Tom Herbert
2016-03-01 18:16 ` Jiri Benc
2016-02-26 7:48 ` [PATCH net-next 2/5] vxlan: move L2 mode initialization to a separate function Jiri Benc
2016-02-26 7:48 ` [PATCH net-next 3/5] vxlan: move fdb code to common location in vxlan_xmit Jiri Benc
2016-02-26 7:48 ` [PATCH net-next 4/5] vxlan: fix too large pskb_may_pull with remote checksum Jiri Benc
2016-02-26 7:48 ` [PATCH net-next 5/5] vxlan: implement GPE in L3 mode Jiri Benc
2016-02-26 22:22 ` Jesse Gross
2016-02-26 23:42 ` Tom Herbert
2016-02-27 19:26 ` Jiri Benc
2016-02-27 19:21 ` Jiri Benc
2016-02-27 19:44 ` Jiri Benc
2016-03-08 22:18 ` Jesse Gross
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=cover.1456472746.git.jbenc@redhat.com \
--to=jbenc@redhat.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).