From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>
Cc: davem@davemloft.net, simon.horman@netronome.com
Subject: [PATCH net-next 0/4] net: sched: support vxlan and erspan options
Date: Tue, 19 Nov 2019 17:31:45 +0800 [thread overview]
Message-ID: <cover.1574155869.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.
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 | 191 +++++++++++++++++++++-
net/sched/cls_flower.c | 252 ++++++++++++++++++++++++++++++
4 files changed, 500 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2019-11-19 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 9:31 Xin Long [this message]
2019-11-19 9:31 ` [PATCH net-next 1/4] net: sched: add vxlan option support to act_tunnel_key Xin Long
2019-11-19 9:31 ` [PATCH net-next 2/4] net: sched: add erspan " Xin Long
2019-11-19 9:31 ` [PATCH net-next 3/4] net: sched: allow flower to match vxlan options Xin Long
2019-11-19 9:31 ` [PATCH net-next 4/4] net: sched: allow flower to match erspan options Xin Long
2019-11-20 0:27 ` [PATCH net-next 2/4] net: sched: add erspan option support to act_tunnel_key Jakub Kicinski
2019-11-20 5:15 ` Xin Long
2019-11-20 0:12 ` [PATCH net-next 1/4] net: sched: add vxlan " Jakub Kicinski
2019-11-20 5:08 ` Xin Long
2019-11-20 17:17 ` Jakub Kicinski
2019-11-21 5:45 ` Xin Long
2019-11-21 15:56 ` David Ahern
2019-11-19 14:18 ` [PATCH net-next 0/4] net: sched: support vxlan and erspan options Roman Mashak
2019-11-19 15:55 ` Xin Long
2019-11-19 16:06 ` Roman Mashak
2019-11-19 16:23 ` 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.1574155869.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.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).