From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: ast@plumgrid.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next v2 0/3] BPF updates
Date: Wed, 30 Sep 2015 01:41:49 +0200 [thread overview]
Message-ID: <cover.1443567433.git.daniel@iogearbox.net> (raw)
Some minor updates to {cls,act}_bpf to retrieve routing realms
and to make skb->priority writable.
Thanks!
v1 -> v2:
- Dropped preclassify patch for now from the series as the
rest is pretty much independent of it
- Rest unchanged, only rebased and already posted Acked-by's kept
Daniel Borkmann (3):
ebpf: migrate bpf_prog's flags to bitfield
sched, bpf: add helper for retrieving routing realms
sched, bpf: make skb->priority writable
arch/arm/net/bpf_jit_32.c | 2 +-
arch/arm64/net/bpf_jit_comp.c | 2 +-
arch/mips/net/bpf_jit.c | 2 +-
arch/powerpc/net/bpf_jit_comp.c | 2 +-
arch/s390/net/bpf_jit_comp.c | 2 +-
arch/sparc/net/bpf_jit_comp.c | 2 +-
arch/x86/net/bpf_jit_comp.c | 2 +-
include/linux/filter.h | 7 +++++--
include/uapi/linux/bpf.h | 7 +++++++
kernel/bpf/core.c | 4 ++++
kernel/bpf/syscall.c | 6 ++++--
net/core/filter.c | 33 ++++++++++++++++++++++++++++++---
net/sched/cls_bpf.c | 8 ++++++--
13 files changed, 63 insertions(+), 16 deletions(-)
--
1.9.3
next reply other threads:[~2015-09-29 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 23:41 Daniel Borkmann [this message]
2015-09-29 23:41 ` [PATCH net-next v2 1/3] ebpf: migrate bpf_prog's flags to bitfield Daniel Borkmann
2015-09-29 23:41 ` [PATCH net-next v2 2/3] sched, bpf: add helper for retrieving routing realms Daniel Borkmann
2015-09-29 23:41 ` [PATCH net-next v2 3/3] sched, bpf: make skb->priority writable Daniel Borkmann
2015-10-03 12:03 ` [PATCH net-next v2 0/3] BPF updates David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-09-08 6:04 Daniel Borkmann
2014-09-10 0:00 ` 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.1443567433.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--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 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).