diff options
author | Alexei Starovoitov <[email protected]> | 2017-04-23 09:01:00 -0700 |
---|---|---|
committer | David S. Miller <[email protected]> | 2017-04-23 15:56:48 -0400 |
commit | e2989ee9746b3f2e78d1a39bbc402d884e8b8bf1 (patch) | |
tree | cd7212755fb126bfec59a78e6c4c3d9a8cecc2bb | |
parent | b0c47807d31deccdfb78a22a0d04dd9785bdb9d3 (diff) |
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: Alexei Starovoitov <[email protected]>
Acked-by: Daniel Borkmann <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
-rw-r--r-- | Documentation/networking/filter.txt | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/Documentation/networking/filter.txt b/Documentation/networking/filter.txt index 683ada5ad81d..b69b205501de 100644 --- a/Documentation/networking/filter.txt +++ b/Documentation/networking/filter.txt @@ -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 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 -architectures. x86-64, aarch64 and s390x perform JIT compilation from eBPF -instruction set, however, future work will migrate other JIT compilers as well, -so that they will profit from the very same benefits. +Currently, the classic BPF format is being used for JITing on most 32-bit +architectures, whereas x86-64, aarch64, s390x, powerpc64, sparc64 perform JIT +compilation from eBPF instruction set. Some core changes of the new internal format: |