All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, stephen@networkplumber.org
Cc: David Ahern <dsahern@gmail.com>, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCHv4 iproute2-next 0/7] iproute2: fully support for geneve/vxlan/erspan options
Date: Mon, 27 Apr 2020 18:27:44 +0800	[thread overview]
Message-ID: <cover.1587983178.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.
v3->v4:
  - Basically we print all options as uint, other than 'data' in
    the 1st patch as a hex string.
  - As Stephen's suggestion, we keep all those options of the same
    format between input and output, and between json and non json.

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    | 382 ++++++++++++++++++++++++++++++++++++++++++++++-
 man/man8/tc-flower.8     |  25 ++++
 man/man8/tc-tunnel_key.8 |  20 ++-
 tc/f_flower.c            | 301 +++++++++++++++++++++++++++++++++++--
 tc/m_tunnel_key.c        | 199 ++++++++++++++++++++++--
 5 files changed, 899 insertions(+), 28 deletions(-)

-- 
2.1.0


             reply	other threads:[~2020-04-27 10:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 10:27 Xin Long [this message]
2020-04-27 10:27 ` [PATCHv4 iproute2-next 1/7] iproute_lwtunnel: add options support for geneve metadata Xin Long
2020-04-27 10:27   ` [PATCHv4 iproute2-next 2/7] iproute_lwtunnel: add options support for vxlan metadata Xin Long
2020-04-27 10:27     ` [PATCHv4 iproute2-next 3/7] iproute_lwtunnel: add options support for erspan metadata Xin Long
2020-04-27 10:27       ` [PATCHv4 iproute2-next 4/7] tc: m_tunnel_key: add options support for vxlan Xin Long
2020-04-27 10:27         ` [PATCHv4 iproute2-next 5/7] tc: m_tunnel_key: add options support for erpsan Xin Long
2020-04-27 10:27           ` [PATCHv4 iproute2-next 6/7] tc: f_flower: add options support for vxlan Xin Long
2020-04-27 10:27             ` [PATCHv4 iproute2-next 7/7] tc: f_flower: add options support for erspan Xin Long
2020-04-29 16:58     ` [PATCHv4 iproute2-next 2/7] iproute_lwtunnel: add options support for vxlan metadata David Ahern
2020-04-30  5:12       ` Xin Long
2020-04-30 16:19         ` David Ahern
2020-04-30 18:09           ` Xin Long
2020-05-01 16:33 ` [PATCHv4 iproute2-next 0/7] iproute2: fully support for geneve/vxlan/erspan options David Ahern

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.1587983178.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=kuba@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.