From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: alexei.starovoitov@gmail.com, tgraf@suug.ch,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/4] BPF support for flow labels
Date: Wed, 9 Mar 2016 03:00:01 +0100 [thread overview]
Message-ID: <cover.1457488298.git.daniel@iogearbox.net> (raw)
This set adds support for tunnel key flow labels for vxlan
and geneve devices in collect meta data mode and eBPF support
for managing these. For details please see individual patches.
Thanks!
Daniel Borkmann (4):
ip_tunnel: add support for setting flow label via collect metadata
vxlan: support setting IPv6 flow label
geneve: support setting IPv6 flow label
bpf: support flow label for bpf_skb_{set,get}_tunnel_key
drivers/net/geneve.c | 35 +++++++++++++++++++++++++++--------
drivers/net/vxlan.c | 24 ++++++++++++++++++++----
include/net/dst_metadata.h | 5 ++++-
include/net/ip_tunnels.h | 4 +++-
include/net/udp_tunnel.h | 4 ++--
include/net/vxlan.h | 1 +
include/uapi/linux/bpf.h | 1 +
include/uapi/linux/if_link.h | 2 ++
net/core/filter.c | 14 ++++++++++++--
net/ipv6/ip6_udp_tunnel.c | 6 +++---
net/tipc/udp_media.c | 2 +-
11 files changed, 76 insertions(+), 22 deletions(-)
--
1.9.3
next reply other threads:[~2016-03-09 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 2:00 Daniel Borkmann [this message]
2016-03-09 2:00 ` [PATCH net-next 1/4] ip_tunnel: add support for setting flow label via collect metadata Daniel Borkmann
2016-03-09 2:00 ` [PATCH net-next 2/4] vxlan: support setting IPv6 flow label Daniel Borkmann
2016-03-09 3:29 ` Tom Herbert
2016-03-09 10:53 ` Daniel Borkmann
2016-03-09 2:00 ` [PATCH net-next 3/4] geneve: " Daniel Borkmann
2016-03-09 3:38 ` Tom Herbert
2016-03-09 2:00 ` [PATCH net-next 4/4] bpf: support flow label for bpf_skb_{set,get}_tunnel_key Daniel Borkmann
2016-03-11 20:14 ` [PATCH net-next 0/4] BPF support for flow labels 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.1457488298.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).