From: Jiri Benc <jbenc@redhat.com>
To: netdev@vger.kernel.org
Cc: dev@openvswitch.org, Pravin Shelar <pshelar@nicira.com>,
Jesse Gross <jesse@nicira.com>
Subject: [PATCH net-next v3 0/2] openvswitch: add IPv6 tunneling support
Date: Mon, 5 Oct 2015 13:09:45 +0200 [thread overview]
Message-ID: <cover.1444041801.git.jbenc@redhat.com> (raw)
This builds on the previous work that added IPv6 support to lwtunnels and
adds IPv6 tunneling support to ovs.
To use IPv6 tunneling, there needs to be a metadata based tunnel net_device
created and added to the ovs bridge. Currently, only vxlan is supported by
the kernel, with geneve to follow shortly. There's no need nor intent to add
a support for this into the vport-vxlan (etc.) compat layer.
---
v3: dropped the last two patches added in v2.
Jiri Benc (2):
openvswitch: add tunnel protocol to sw_flow_key
openvswitch: netlink attributes for IPv6 tunneling
include/uapi/linux/openvswitch.h | 2 +
net/openvswitch/flow.c | 4 +-
net/openvswitch/flow.h | 1 +
net/openvswitch/flow_netlink.c | 129 +++++++++++++++++++++++++++------------
net/openvswitch/flow_table.c | 2 +-
5 files changed, 97 insertions(+), 41 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-10-05 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 11:09 Jiri Benc [this message]
2015-10-05 11:09 ` [PATCH net-next v3 1/2] openvswitch: add tunnel protocol to sw_flow_key Jiri Benc
[not found] ` <a8a99b9e11a824ca078f92f8e13aef5955b2a6d4.1444041801.git.jbenc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-05 12:23 ` Thomas Graf
2015-10-05 11:09 ` [PATCH net-next v3 2/2] openvswitch: netlink attributes for IPv6 tunneling Jiri Benc
2015-10-05 12:23 ` Thomas Graf
2015-10-07 11:18 ` [PATCH net-next v3 0/2] openvswitch: add IPv6 tunneling support 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=cover.1444041801.git.jbenc@redhat.com \
--to=jbenc@redhat.com \
--cc=dev@openvswitch.org \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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).