* [PATCH] bpf: doc: correct arch list for supported eBPF JIT
@ 2015-11-07 5:38 Yang Shi
2015-11-08 0:47 ` Daniel Borkmann
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Yang Shi @ 2015-11-07 5:38 UTC (permalink / raw)
To: ast, daniel; +Cc: linux-kernel, netdev, linaro-kernel, yang.shi
aarch64 and s390x support eBPF JIT too, correct document to reflect this and
avoid any confusion.
Signed-off-by: Yang Shi <yang.shi@linaro.org>
---
Documentation/networking/filter.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/filter.txt b/Documentation/networking/filter.txt
index 135581f..96da119 100644
--- a/Documentation/networking/filter.txt
+++ b/Documentation/networking/filter.txt
@@ -596,9 +596,9 @@ 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. Only x86-64 performs 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.
+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.
Some core changes of the new internal format:
--
2.0.2
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH] bpf: doc: correct arch list for supported eBPF JIT
2015-11-07 5:38 [PATCH] bpf: doc: correct arch list for supported eBPF JIT Yang Shi
@ 2015-11-08 0:47 ` Daniel Borkmann
2015-11-08 2:28 ` Alexei Starovoitov
2015-11-08 18:22 ` David Miller
2 siblings, 0 replies; 4+ messages in thread
From: Daniel Borkmann @ 2015-11-08 0:47 UTC (permalink / raw)
To: Yang Shi, ast; +Cc: linux-kernel, netdev, linaro-kernel
On 11/07/2015 06:38 AM, Yang Shi wrote:
> aarch64 and s390x support eBPF JIT too, correct document to reflect this and
> avoid any confusion.
>
> Signed-off-by: Yang Shi <yang.shi@linaro.org>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] bpf: doc: correct arch list for supported eBPF JIT
2015-11-07 5:38 [PATCH] bpf: doc: correct arch list for supported eBPF JIT Yang Shi
2015-11-08 0:47 ` Daniel Borkmann
@ 2015-11-08 2:28 ` Alexei Starovoitov
2015-11-08 18:22 ` David Miller
2 siblings, 0 replies; 4+ messages in thread
From: Alexei Starovoitov @ 2015-11-08 2:28 UTC (permalink / raw)
To: Yang Shi; +Cc: ast, daniel, linux-kernel, netdev, linaro-kernel
On Fri, Nov 06, 2015 at 09:38:58PM -0800, Yang Shi wrote:
> aarch64 and s390x support eBPF JIT too, correct document to reflect this and
> avoid any confusion.
>
> Signed-off-by: Yang Shi <yang.shi@linaro.org>
Thanks
Acked-by: Alexei Starovoitov <ast@kernel.org>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] bpf: doc: correct arch list for supported eBPF JIT
2015-11-07 5:38 [PATCH] bpf: doc: correct arch list for supported eBPF JIT Yang Shi
2015-11-08 0:47 ` Daniel Borkmann
2015-11-08 2:28 ` Alexei Starovoitov
@ 2015-11-08 18:22 ` David Miller
2 siblings, 0 replies; 4+ messages in thread
From: David Miller @ 2015-11-08 18:22 UTC (permalink / raw)
To: yang.shi; +Cc: ast, daniel, linux-kernel, netdev, linaro-kernel
From: Yang Shi <yang.shi@linaro.org>
Date: Fri, 6 Nov 2015 21:38:58 -0800
> aarch64 and s390x support eBPF JIT too, correct document to reflect this and
> avoid any confusion.
>
> Signed-off-by: Yang Shi <yang.shi@linaro.org>
Applied, thanks.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-11-08 18:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-07 5:38 [PATCH] bpf: doc: correct arch list for supported eBPF JIT Yang Shi
2015-11-08 0:47 ` Daniel Borkmann
2015-11-08 2:28 ` Alexei Starovoitov
2015-11-08 18:22 ` David Miller
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).