Commit e2989ee9 authored by Alexei Starovoitov's avatar Alexei Starovoitov Committed by David S. Miller

bpf, doc: update list of architectures that do eBPF JIT

update the list and remove 'in the future' statement,
since all still alive 64-bit architectures now do eBPF JIT.
Signed-off-by: default avatarAlexei Starovoitov <ast@kernel.org>
Acked-by: default avatarDaniel Borkmann <daniel@iogearbox.net>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent b0c47807
...@@ -595,10 +595,9 @@ got from bpf_prog_create(), and 'ctx' the given context (e.g. ...@@ -595,10 +595,9 @@ got from bpf_prog_create(), and 'ctx' the given context (e.g.
skb pointer). All constraints and restrictions from bpf_check_classic() apply skb pointer). All constraints and restrictions from bpf_check_classic() apply
before a conversion to the new layout is being done behind the scenes! before a conversion to the new layout is being done behind the scenes!
Currently, the classic BPF format is being used for JITing on most of the Currently, the classic BPF format is being used for JITing on most 32-bit
architectures. x86-64, aarch64 and s390x perform JIT compilation from eBPF architectures, whereas x86-64, aarch64, s390x, powerpc64, sparc64 perform JIT
instruction set, however, future work will migrate other JIT compilers as well, compilation from eBPF instruction set.
so that they will profit from the very same benefits.
Some core changes of the new internal format: Some core changes of the new internal format:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment