From: Simon Horman <simon.horman@netronome.com>
To: Jiri Pirko <jiri@mellanox.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
Simon Horman <simon.horman@netronome.com>
Subject: [PATCH/RFC net-next 0/3] introduce Geneve options support in TC tunnel key
Date: Tue, 6 Mar 2018 18:08:02 +0100 [thread overview]
Message-ID: <20180306170805.19500-1-simon.horman@netronome.com> (raw)
Hi all,
This set adds Geneve options support to the TC tunnel key action.
Options TLVs are exposed to userspace using a list of netlink attributes
with each option described using attributes for class, type and data.
The series also enhances the tunnel key action to use extended ack.
Simon Horman (3):
net/sched: act_tunnel_key: disambiguate metadata dst error cases
net/sched: act_tunnel_key: add extended ack support
net/sched: add tunnel option support to act_tunnel_key
include/uapi/linux/tc_act/tc_tunnel_key.h | 26 ++++
net/sched/act_tunnel_key.c | 212 ++++++++++++++++++++++++++++--
2 files changed, 230 insertions(+), 8 deletions(-)
--
2.11.0
next reply other threads:[~2018-03-06 17:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 17:08 Simon Horman [this message]
2018-03-06 17:08 ` [PATCH/RFC 1/3] net/sched: act_tunnel_key: disambiguate metadata dst error cases Simon Horman
2018-03-06 17:08 ` [PATCH/RFC 2/3] net/sched: act_tunnel_key: add extended ack support Simon Horman
2018-03-09 11:22 ` Jiri Benc
2018-03-22 11:49 ` Simon Horman
2018-03-06 17:08 ` [PATCH/RFC 3/3] net/sched: add tunnel option support to act_tunnel_key Simon Horman
2018-03-09 11:53 ` Jiri Benc
2018-03-22 11:53 ` Simon Horman
2018-03-06 17:11 ` [PATCH/RFC net-next 0/3] introduce Geneve options support in TC tunnel key Or Gerlitz
2018-03-06 17:16 ` Simon Horman
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=20180306170805.19500-1-simon.horman@netronome.com \
--to=simon.horman@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=xiyou.wangcong@gmail.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).