From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: jiri@resnulli.us, ast@plumgrid.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/2] act_bpf update
Date: Fri, 20 Mar 2015 15:11:10 +0100 [thread overview]
Message-ID: <cover.1426859241.git.daniel@iogearbox.net> (raw)
This set adds native eBPF support also to act_bpf and thus covers tc
with eBPF in the classifier *and* action part.
A link to iproute2 preview has been provided in patch 2 and the code
will be pushed out after Stephen has processed the classifier part
and helper bits for tc.
This set depends on ced585c83b27 ("act_bpf: allow non-default TC_ACT
opcodes as BPF exec outcome"), so a net into net-next merge would be
required first. Hope that's fine by you, Dave. ;)
Thanks a lot!
Daniel Borkmann (2):
ebpf: add sched_act_type and map it to sk_filter's verifier ops
act_bpf: add initial eBPF support for actions
include/net/tc_act/tc_bpf.h | 6 +-
include/uapi/linux/bpf.h | 1 +
include/uapi/linux/tc_act/tc_bpf.h | 2 +
kernel/bpf/verifier.c | 1 +
net/core/filter.c | 6 +
net/sched/act_bpf.c | 295 ++++++++++++++++++++++++++-----------
6 files changed, 228 insertions(+), 83 deletions(-)
--
1.9.3
next reply other threads:[~2015-03-20 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 14:11 Daniel Borkmann [this message]
2015-03-20 14:11 ` [PATCH net-next 1/2] ebpf: add sched_act_type and map it to sk_filter's verifier ops Daniel Borkmann
2015-03-20 14:21 ` Jiri Pirko
2015-03-20 21:11 ` Alexei Starovoitov
2015-03-20 14:11 ` [PATCH net-next 2/2] act_bpf: add initial eBPF support for actions Daniel Borkmann
2015-03-20 14:30 ` Jiri Pirko
2015-03-20 21:21 ` Alexei Starovoitov
2015-03-20 20:22 ` [PATCH net-next 0/2] act_bpf update David Miller
2015-03-20 21:10 ` Daniel Borkmann
2015-03-20 21:26 ` Alexei Starovoitov
2015-03-20 22:21 ` David Miller
2015-03-20 22:45 ` Daniel Borkmann
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.1426859241.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.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.