From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org
Cc: john.fastabend@gmail.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH rfc bpf-next 0/8] Optimize BPF tail calls for direct jumps
Date: Fri, 15 Nov 2019 02:03:54 +0100 [thread overview]
Message-ID: <cover.1573779287.git.daniel@iogearbox.net> (raw)
This gets rid of indirect jumps for BPF tail calls whenever possible.
See patch 7/8 for more general details. This is on top of Alexei's
'[v4,bpf-next,00/20] Introduce BPF trampoline' series [0]. For non-RFC
I'll still massage commit messages a bit and expand the existing set
of tail call tests with a few more kselftest cases.
Thanks,
Daniel
[0] https://patchwork.ozlabs.org/project/netdev/list/?series=142923
Daniel Borkmann (8):
bpf, x86: generalize and extend bpf_arch_text_poke for direct jumps
bpf: add bpf_prog_under_eviction helper
bpf: move bpf_free_used_maps into sleepable section
bpf: move owner type,jited info into array auxillary data
bpf: add jit poke descriptor mock-up for jit images
bpf: add poke dependency tracking for prog array maps
bpf, x86: emit patchable direct jump as tail call
bpf: constant map key tracking for prog array pokes
arch/x86/net/bpf_jit_comp.c | 234 ++++++++++++++++++++++++-----------
include/linux/bpf.h | 85 +++++++++++--
include/linux/bpf_verifier.h | 1 +
include/linux/filter.h | 10 ++
kernel/bpf/arraymap.c | 152 ++++++++++++++++++++++-
kernel/bpf/core.c | 73 ++++++++++-
kernel/bpf/map_in_map.c | 5 +-
kernel/bpf/syscall.c | 41 ++----
kernel/bpf/verifier.c | 98 +++++++++++++++
9 files changed, 578 insertions(+), 121 deletions(-)
--
2.21.0
next reply other threads:[~2019-11-15 1:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 1:03 Daniel Borkmann [this message]
2019-11-15 1:03 ` [PATCH rfc bpf-next 1/8] bpf, x86: generalize and extend bpf_arch_text_poke for direct jumps Daniel Borkmann
2019-11-15 23:22 ` Andrii Nakryiko
2019-11-15 23:42 ` Daniel Borkmann
2019-11-16 0:01 ` Andrii Nakryiko
2019-11-15 1:03 ` [PATCH rfc bpf-next 2/8] bpf: add bpf_prog_under_eviction helper Daniel Borkmann
2019-11-15 1:03 ` [PATCH rfc bpf-next 3/8] bpf: move bpf_free_used_maps into sleepable section Daniel Borkmann
2019-11-15 23:32 ` Andrii Nakryiko
2019-11-15 1:03 ` [PATCH rfc bpf-next 4/8] bpf: move owner type,jited info into array auxillary data Daniel Borkmann
2019-11-15 23:19 ` Andrii Nakryiko
2019-11-15 1:03 ` [PATCH rfc bpf-next 5/8] bpf: add jit poke descriptor mock-up for jit images Daniel Borkmann
2019-11-18 18:17 ` Andrii Nakryiko
2019-11-18 18:43 ` Daniel Borkmann
2019-11-15 1:04 ` [PATCH rfc bpf-next 6/8] bpf: add poke dependency tracking for prog array maps Daniel Borkmann
2019-11-18 17:39 ` Andrii Nakryiko
2019-11-18 18:39 ` Daniel Borkmann
2019-11-18 18:46 ` Andrii Nakryiko
2019-11-18 21:35 ` Daniel Borkmann
2019-11-15 1:04 ` [PATCH rfc bpf-next 7/8] bpf, x86: emit patchable direct jump as tail call Daniel Borkmann
2019-11-15 3:23 ` Alexei Starovoitov
2019-11-15 7:27 ` Daniel Borkmann
2019-11-15 1:04 ` [PATCH rfc bpf-next 8/8] bpf: constant map key tracking for prog array pokes Daniel Borkmann
2019-11-15 4:29 ` Alexei Starovoitov
2019-11-15 7:13 ` Daniel Borkmann
2019-11-15 16:33 ` Alexei Starovoitov
2019-11-15 16:49 ` Daniel Borkmann
2019-11-18 18:11 ` Andrii Nakryiko
2019-11-18 21: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.1573779287.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.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 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.