From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: ast@fb.com, holzheu@linux.vnet.ibm.com,
naveen.n.rao@linux.vnet.ibm.com, jakub.kicinski@netronome.com,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next v2 0/9] Add BPF_J{LT,LE,SLT,SLE} instructions
Date: Thu, 10 Aug 2017 01:39:54 +0200 [thread overview]
Message-ID: <cover.1502320623.git.daniel@iogearbox.net> (raw)
This set adds BPF_J{LT,LE,SLT,SLE} instructions to the BPF
insn set, interpreter, JIT hardening code and all JITs are
also updated to support the new instructions. Basic idea is
to reduce register pressure by avoiding BPF_J{GT,GE,SGT,SGE}
rewrites. Removing the workaround for the rewrites in LLVM,
this can result in shorter BPF programs, less stack usage
and less verification complexity. First patch provides some
more details on rationale and integration.
Thanks a lot!
v1 -> v2:
- Reworded commit msg in patch 1
Daniel Borkmann (9):
bpf: add BPF_J{LT,LE,SLT,SLE} instructions
bpf, x86: implement jiting of BPF_J{LT,LE,SLT,SLE}
bpf, arm64: implement jiting of BPF_J{LT,LE,SLT,SLE}
bpf, sparc64: implement jiting of BPF_J{LT, LE, SLT, SLE}
bpf, s390x: implement jiting of BPF_J{LT,LE,SLT,SLE}
bpf, ppc64: implement jiting of BPF_J{LT,LE,SLT,SLE}
bpf, nfp: implement jiting of BPF_J{LT,LE}
bpf: enable BPF_J{LT,LE,SLT,SLE} opcodes in verifier
bpf: add test cases for new BPF_J{LT, LE, SLT, SLE} instructions
Documentation/networking/filter.txt | 4 +
arch/arm64/net/bpf_jit.h | 4 +
arch/arm64/net/bpf_jit_comp.c | 20 ++
arch/powerpc/net/bpf_jit.h | 1 +
arch/powerpc/net/bpf_jit_comp64.c | 20 ++
arch/s390/net/bpf_jit_comp.c | 24 ++
arch/sparc/net/bpf_jit_comp_64.c | 34 +++
arch/x86/net/bpf_jit_comp.c | 26 ++
drivers/net/ethernet/netronome/nfp/bpf/jit.c | 24 ++
include/uapi/linux/bpf.h | 5 +
kernel/bpf/core.c | 60 +++++
kernel/bpf/verifier.c | 62 ++++-
lib/test_bpf.c | 364 +++++++++++++++++++++++++++
net/core/filter.c | 21 +-
tools/include/uapi/linux/bpf.h | 5 +
tools/testing/selftests/bpf/test_verifier.c | 313 +++++++++++++++++++++++
16 files changed, 979 insertions(+), 8 deletions(-)
--
1.9.3
next reply other threads:[~2017-08-09 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 23:39 Daniel Borkmann [this message]
2017-08-09 23:39 ` [PATCH net-next v2 1/9] bpf: add BPF_J{LT,LE,SLT,SLE} instructions Daniel Borkmann
2017-08-09 23:39 ` [PATCH net-next v2 2/9] bpf, x86: implement jiting of BPF_J{LT,LE,SLT,SLE} Daniel Borkmann
2017-08-09 23:39 ` [PATCH net-next v2 3/9] bpf, arm64: " Daniel Borkmann
2017-08-09 23:39 ` [PATCH net-next v2 4/9] bpf, sparc64: implement jiting of BPF_J{LT, LE, SLT, SLE} Daniel Borkmann
2017-08-09 23:39 ` [PATCH net-next v2 5/9] bpf, s390x: implement jiting of BPF_J{LT,LE,SLT,SLE} Daniel Borkmann
2017-08-09 23:40 ` [PATCH net-next v2 6/9] bpf, ppc64: " Daniel Borkmann
2017-08-09 23:40 ` [PATCH net-next v2 7/9] bpf, nfp: implement jiting of BPF_J{LT,LE} Daniel Borkmann
2017-08-09 23:40 ` [PATCH net-next v2 8/9] bpf: enable BPF_J{LT,LE,SLT,SLE} opcodes in verifier Daniel Borkmann
2017-08-09 23:40 ` [PATCH net-next v2 9/9] bpf: add test cases for new BPF_J{LT, LE, SLT, SLE} instructions Daniel Borkmann
2017-08-09 23:55 ` [PATCH net-next v2 0/9] Add BPF_J{LT,LE,SLT,SLE} instructions 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.1502320623.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=holzheu@linux.vnet.ibm.com \
--cc=jakub.kicinski@netronome.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--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).