From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, stephen@networkplumber.org
Cc: Simon Horman <simon.horman@netronome.com>,
David Ahern <dsahern@gmail.com>
Subject: [PATCHv3 iproute2-next 0/7] iproute2: fully support for geneve/vxlan/erspan options
Date: Fri, 14 Feb 2020 18:30:44 +0800 [thread overview]
Message-ID: <cover.1581676056.git.lucien.xin@gmail.com> (raw)
Patch 1-3 add the geneve/vxlan/erspan options support for
iproute_lwtunnel, and Patch 4-5 add the vxlan/erspan options
for tc m_tunnel_key, and Patch 6-7 add the vxlan/erspan options
for tc f_flower.
In kernel space, these features have been supported since these
patchsets:
https://patchwork.ozlabs.org/cover/1190172/
https://patchwork.ozlabs.org/cover/1198854/
v1->v2:
- improve the bash commands in changelog as David A. suggested.
- use PRINT_ANY to support dummping with json format as Stephen
suggested.
v2->v3:
- implement proper JSON array for opts as Stephen suggested.
Xin Long (7):
iproute_lwtunnel: add options support for geneve metadata
iproute_lwtunnel: add options support for vxlan metadata
iproute_lwtunnel: add options support for erspan metadata
tc: m_tunnel_key: add options support for vxlan
tc: m_tunnel_key: add options support for erpsan
tc: f_flower: add options support for vxlan
tc: f_flower: add options support for erspan
ip/iproute_lwtunnel.c | 398 ++++++++++++++++++++++++++++++++++++++++++++++-
man/man8/tc-flower.8 | 26 ++++
man/man8/tc-tunnel_key.8 | 20 ++-
tc/f_flower.c | 301 +++++++++++++++++++++++++++++++++--
tc/m_tunnel_key.c | 205 ++++++++++++++++++++++--
5 files changed, 922 insertions(+), 28 deletions(-)
--
2.1.0
next reply other threads:[~2020-02-14 10:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 10:30 Xin Long [this message]
2020-02-14 10:30 ` [PATCHv3 iproute2-next 1/7] iproute_lwtunnel: add options support for geneve metadata Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 2/7] iproute_lwtunnel: add options support for vxlan metadata Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 3/7] iproute_lwtunnel: add options support for erspan metadata Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 4/7] tc: m_tunnel_key: add options support for vxlan Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 5/7] tc: m_tunnel_key: add options support for erpsan Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 6/7] tc: f_flower: add options support for vxlan Xin Long
2020-02-14 10:30 ` [PATCHv3 iproute2-next 7/7] tc: f_flower: add options support for erspan Xin Long
2020-02-14 16:13 ` [PATCHv3 iproute2-next 3/7] iproute_lwtunnel: add options support for erspan metadata Stephen Hemminger
2020-02-14 17:40 ` Xin Long
2020-02-15 0:21 ` Stephen Hemminger
2020-02-15 4:18 ` Xin Long
2020-02-15 16:51 ` David Ahern
2020-02-16 6:38 ` Xin Long
2020-02-17 19:53 ` David Ahern
2020-02-17 21:02 ` Stephen Hemminger
2020-02-18 4:29 ` Xin Long
2020-04-19 8:39 ` Xin Long
2020-04-19 22:28 ` David Ahern
2020-04-23 11:06 ` Xin Long
2020-04-26 18:29 ` David Ahern
2020-04-27 5:51 ` Xin Long
2020-04-23 15:23 ` Stephen Hemminger
2020-04-23 18:03 ` Jakub Kicinski
2020-04-27 12:38 ` David Ahern
2020-04-27 23:07 ` Stephen Hemminger
2020-04-28 7:22 ` Xin Long
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.1581676056.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--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).