From: Michael Ellerman <mpe@ellerman.id.au>
To: ast@kernel.org, daniel@iogearbox.net
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2] bpf: Update sysctl documentation to list all supported architectures
Date: Thu, 17 Aug 2017 20:30:39 +1000 [thread overview]
Message-ID: <1502965839-23115-1-git-send-email-mpe@ellerman.id.au> (raw)
The sysctl documentation states that the JIT is only available on
x86_64, which is no longer correct.
Update the list, and break it out to indicate which architectures
support the cBPF JIT (via HAVE_CBPF_JIT) or the eBPF JIT
(HAVE_EBPF_JIT).
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
Documentation/sysctl/net.txt | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
v2: Split the list based on cBPF vs eBPF.
diff --git a/Documentation/sysctl/net.txt b/Documentation/sysctl/net.txt
index 14db18c970b1..b9c3c6078010 100644
--- a/Documentation/sysctl/net.txt
+++ b/Documentation/sysctl/net.txt
@@ -36,8 +36,23 @@ bpf_jit_enable
--------------
This enables Berkeley Packet Filter Just in Time compiler.
-Currently supported on x86_64 architecture, bpf_jit provides a framework
-to speed packet filtering, the one used by tcpdump/libpcap for example.
+
+There are two flavors of JIT, the new eBPF JIT supported on:
+ - x86_64
+ - arm64
+ - ppc64
+ - sparc64
+ - mips64
+
+And the older cBPF JIT supported on:
+ - arm
+ - mips
+ - ppc
+ - sparc
+
+The BPF JIT provides a framework to speed packet filtering, the one used by
+tcpdump/libpcap for example.
+
Values :
0 - disable the JIT (default value)
1 - enable the JIT
--
2.7.4
next reply other threads:[~2017-08-17 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:30 Michael Ellerman [this message]
2017-08-17 11:50 ` Daniel Borkmann
2017-08-18 1:27 ` Michael Ellerman
2017-08-17 17:09 ` 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=1502965839-23115-1-git-send-email-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®