From: Xin Long <lucien.xin@gmail•com>
To: network dev <netdev@vger•kernel.org>
Cc: davem@davemloft•net, simon.horman@netronome•com,
jakub.kicinski@netronome•com
Subject: [PATCHv2 net-next 0/4] net: sched: support vxlan and erspan options
Date: Thu, 21 Nov 2019 18:03:25 +0800 [thread overview]
Message-ID: <cover.1574330535.git.lucien.xin@gmail.com> (raw)
This patchset is to add vxlan and erspan options support in
cls_flower and act_tunnel_key. The form is pretty much like
geneve_opts in:
https://patchwork.ozlabs.org/patch/935272/
https://patchwork.ozlabs.org/patch/954564/
but only one option is allowed for vxlan and erspan.
v1->v2:
- see each patch changelog.
Xin Long (4):
net: sched: add vxlan option support to act_tunnel_key
net: sched: add erspan option support to act_tunnel_key
net: sched: allow flower to match vxlan options
net: sched: allow flower to match erspan options
include/uapi/linux/pkt_cls.h | 29 ++++
include/uapi/linux/tc_act/tc_tunnel_key.h | 29 ++++
net/sched/act_tunnel_key.c | 203 +++++++++++++++++++++++-
net/sched/cls_flower.c | 254 ++++++++++++++++++++++++++++++
4 files changed, 514 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2019-11-21 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 10:03 Xin Long [this message]
2019-11-21 10:03 ` [PATCHv2 net-next 1/4] net: sched: add vxlan option support to act_tunnel_key Xin Long
2019-11-21 10:03 ` [PATCHv2 net-next 2/4] net: sched: add erspan " Xin Long
2019-11-21 10:03 ` [PATCHv2 net-next 3/4] net: sched: allow flower to match vxlan options Xin Long
2019-11-21 10:03 ` [PATCHv2 net-next 4/4] net: sched: allow flower to match erspan options Xin Long
2019-11-21 18:54 ` [PATCHv2 net-next 0/4] net: sched: support vxlan and " Jakub Kicinski
2019-11-21 19:46 ` 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.1574330535.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jakub.kicinski@netronome$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=simon.horman@netronome$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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