From: "John W. Linville" <linville@tuxdriver.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jesse Gross <jesse@nicira.com>, Andy Zhou <azhou@nicira.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Alexander Duyck <alexander.h.duyck@redhat.com>
Subject: [RFC] add GENEVE netdev tunnel driver
Date: Thu, 2 Apr 2015 15:17:01 -0400 [thread overview]
Message-ID: <1428002227-11636-1-git-send-email-linville@tuxdriver.com> (raw)
This 5-patch kernel series adds a netdev implementation of a GENEVE
tunnel driver, and the single iproute2 patch enables creation and
such for those netdevs. This makes use of the existing GENEVE
infrastructure already used by the OVS code. The net/ipv4/geneve.c
file is renamed as net/ipv4/libgeneve.c as part of these changes.
The overall structure of the GENEVE netdev driver is strongly
influenced by the VXLAN netdev driver. This is not surprising, as the
two drivers are intended to serve similar purposes. As development
of the GENEVE driver continues, it is likely that those similarities
will grow stronger.
The current implementation is very simple, restricting itself to a
single GENEVE tunnel netdev per net namespace. This is due only to
the simplicity of the implementation, and no such limit is inherent
to GENEVE in any way. I am releasing this as an RFC patch series at
this point both as a means of reporting progress on this effort and
in hopes of collecting useful feedback.
Using the included iproute2 patch, a GENEVE tunnel is created thusly:
ip link add dev gnv0 type geneve remote 192.168.22.1 vni 1234
ip link set gnv0 up
ip addr add 10.1.1.1/24 dev gnv0
After a corresponding tunnel interface is created at the link partner,
traffic should proceed as expected.
Please let me know if anyone has problems. I look forward to your
feedback!
John
next reply other threads:[~2015-04-02 19:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 19:17 John W. Linville [this message]
2015-04-02 19:17 ` [RFC PATCH 1/5] geneve: remove MODULE_ALIAS_RTNL_LINK from net/ipv4/geneve.c John W. Linville
2015-04-02 23:39 ` Stephen Hemminger
2015-04-03 12:17 ` Jiri Pirko
2015-04-03 14:27 ` John W. Linville
2015-04-02 19:17 ` [RFC PATCH 2/5] geneve: move definition of geneve_hdr() to geneve.h John W. Linville
2015-04-02 19:17 ` [RFC PATCH 3/5] Rename support library for geneve John W. Linville
2015-04-03 0:05 ` Cong Wang
2015-04-03 14:40 ` John W. Linville
2015-04-03 15:54 ` Nicolas Dichtel
2015-04-03 18:25 ` John W. Linville
2015-04-02 19:17 ` [RFC PATCH 4/5] libgeneve: identify as driver library in modules description John W. Linville
2015-04-02 19:17 ` [RFC PATCH 5/5] geneve: add initial netdev driver for GENEVE tunnels John W. Linville
2015-04-02 20:20 ` Jiri Pirko
2015-04-03 14:57 ` John W. Linville
2015-04-03 15:07 ` John W. Linville
2015-04-03 15:20 ` Jiri Pirko
2015-04-03 18:31 ` John W. Linville
2015-04-03 5:55 ` Simon Horman
2015-04-03 14:41 ` John W. Linville
2015-04-03 21:05 ` Jesse Gross
2015-04-04 1:01 ` Francois Romieu
2015-04-06 18:06 ` Jesse Gross
2015-04-06 18:44 ` John W. Linville
2015-04-06 20:44 ` Francois Romieu
2015-04-06 18:43 ` John W. Linville
2015-04-06 22:52 ` Jesse Gross
2015-04-02 19:17 ` [RFC PATCH] iproute2: GENEVE support John W. Linville
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=1428002227-11636-1-git-send-email-linville@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=alexander.h.duyck@redhat.com \
--cc=azhou@nicira.com \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).