From: Daniel Borkmann <daniel@iogearbox.net> To: bjorn.topel@gmail.com, linux-riscv@lists.infradead.org, ast@kernel.org, netdev@vger.kernel.org Cc: palmer@sifive.com, hch@infradead.org Subject: Re: [PATCH bpf-next 3/3] bpf, doc: add RISC-V to filter.txt Date: Mon, 4 Feb 2019 21:09:03 +0100 [thread overview] Message-ID: <d033e68a-b520-c25d-e951-761693c16fe7@iogearbox.net> (raw) In-Reply-To: <20190203115132.8766-4-bjorn.topel@gmail.com> On 02/03/2019 12:51 PM, bjorn.topel@gmail.com wrote: > From: Björn Töpel <bjorn.topel@gmail.com> > > Update Documentation/networking/filter.txt to mention RISC-V. > > Signed-off-by: Björn Töpel <bjorn.topel@gmail.com> Nit: in Documentation/sysctl/net.txt under bpf_jit_enable there is also a concrete list of eBPF/cBPF JITs, would be good to add riscv64 there as well. > Documentation/networking/filter.txt | 16 +++++++++------- > 1 file changed, 9 insertions(+), 7 deletions(-) > > diff --git a/Documentation/networking/filter.txt b/Documentation/networking/filter.txt > index 01603bc2eff1..b5e060edfc38 100644 > --- a/Documentation/networking/filter.txt > +++ b/Documentation/networking/filter.txt > @@ -464,10 +464,11 @@ breakpoints: 0 1 > JIT compiler > ------------ > > -The Linux kernel has a built-in BPF JIT compiler for x86_64, SPARC, PowerPC, > -ARM, ARM64, MIPS and s390 and can be enabled through CONFIG_BPF_JIT. The JIT > -compiler is transparently invoked for each attached filter from user space > -or for internal kernel users if it has been previously enabled by root: > +The Linux kernel has a built-in BPF JIT compiler for x86_64, SPARC, > +PowerPC, ARM, ARM64, MIPS, RISC-V and s390 and can be enabled through > +CONFIG_BPF_JIT. The JIT compiler is transparently invoked for each > +attached filter from user space or for internal kernel users if it has > +been previously enabled by root: > > echo 1 > /proc/sys/net/core/bpf_jit_enable > > @@ -603,9 +604,10 @@ 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 32-bit > -architectures, whereas x86-64, aarch64, s390x, powerpc64, sparc64, arm32 perform > -JIT compilation from eBPF instruction set. > +Currently, the classic BPF format is being used for JITing on most > +32-bit architectures, whereas x86-64, aarch64, s390x, powerpc64, > +sparc64, arm32, riscv (RV64G) perform JIT compilation from eBPF > +instruction set. > > Some core changes of the new internal format: > >
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <daniel@iogearbox.net> To: bjorn.topel@gmail.com, linux-riscv@lists.infradead.org, ast@kernel.org, netdev@vger.kernel.org Cc: hch@infradead.org, palmer@sifive.com Subject: Re: [PATCH bpf-next 3/3] bpf, doc: add RISC-V to filter.txt Date: Mon, 4 Feb 2019 21:09:03 +0100 [thread overview] Message-ID: <d033e68a-b520-c25d-e951-761693c16fe7@iogearbox.net> (raw) In-Reply-To: <20190203115132.8766-4-bjorn.topel@gmail.com> On 02/03/2019 12:51 PM, bjorn.topel@gmail.com wrote: > From: Björn Töpel <bjorn.topel@gmail.com> > > Update Documentation/networking/filter.txt to mention RISC-V. > > Signed-off-by: Björn Töpel <bjorn.topel@gmail.com> Nit: in Documentation/sysctl/net.txt under bpf_jit_enable there is also a concrete list of eBPF/cBPF JITs, would be good to add riscv64 there as well. > Documentation/networking/filter.txt | 16 +++++++++------- > 1 file changed, 9 insertions(+), 7 deletions(-) > > diff --git a/Documentation/networking/filter.txt b/Documentation/networking/filter.txt > index 01603bc2eff1..b5e060edfc38 100644 > --- a/Documentation/networking/filter.txt > +++ b/Documentation/networking/filter.txt > @@ -464,10 +464,11 @@ breakpoints: 0 1 > JIT compiler > ------------ > > -The Linux kernel has a built-in BPF JIT compiler for x86_64, SPARC, PowerPC, > -ARM, ARM64, MIPS and s390 and can be enabled through CONFIG_BPF_JIT. The JIT > -compiler is transparently invoked for each attached filter from user space > -or for internal kernel users if it has been previously enabled by root: > +The Linux kernel has a built-in BPF JIT compiler for x86_64, SPARC, > +PowerPC, ARM, ARM64, MIPS, RISC-V and s390 and can be enabled through > +CONFIG_BPF_JIT. The JIT compiler is transparently invoked for each > +attached filter from user space or for internal kernel users if it has > +been previously enabled by root: > > echo 1 > /proc/sys/net/core/bpf_jit_enable > > @@ -603,9 +604,10 @@ 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 32-bit > -architectures, whereas x86-64, aarch64, s390x, powerpc64, sparc64, arm32 perform > -JIT compilation from eBPF instruction set. > +Currently, the classic BPF format is being used for JITing on most > +32-bit architectures, whereas x86-64, aarch64, s390x, powerpc64, > +sparc64, arm32, riscv (RV64G) perform JIT compilation from eBPF > +instruction set. > > Some core changes of the new internal format: > > _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-02-04 20:09 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-03 11:51 [PATCH bpf-next 0/3] Add RISC-V (RV64G) BPF JIT bjorn.topel 2019-02-03 11:51 ` bjorn.topel 2019-02-03 11:51 ` [PATCH bpf-next 1/3] bpf, riscv: add BPF JIT for RV64G bjorn.topel 2019-02-03 11:51 ` bjorn.topel 2019-02-03 17:08 ` David Miller 2019-02-03 17:08 ` David Miller 2019-02-04 20:06 ` Daniel Borkmann 2019-02-04 20:06 ` Daniel Borkmann 2019-02-04 20:27 ` Björn Töpel 2019-02-04 20:27 ` Björn Töpel 2019-02-03 11:51 ` [PATCH bpf-next 2/3] MAINTAINERS: add RISC-V BPF JIT maintainer bjorn.topel 2019-02-03 11:51 ` bjorn.topel 2019-02-03 17:08 ` David Miller 2019-02-03 17:08 ` David Miller 2019-02-03 11:51 ` [PATCH bpf-next 3/3] bpf, doc: add RISC-V to filter.txt bjorn.topel 2019-02-03 11:51 ` bjorn.topel 2019-02-03 17:08 ` David Miller 2019-02-03 17:08 ` David Miller 2019-02-04 20:09 ` Daniel Borkmann [this message] 2019-02-04 20:09 ` Daniel Borkmann 2019-02-04 20:16 ` Björn Töpel 2019-02-04 20:16 ` Björn Töpel
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=d033e68a-b520-c25d-e951-761693c16fe7@iogearbox.net \ --to=daniel@iogearbox.net \ --cc=ast@kernel.org \ --cc=bjorn.topel@gmail.com \ --cc=hch@infradead.org \ --cc=linux-riscv@lists.infradead.org \ --cc=netdev@vger.kernel.org \ --cc=palmer@sifive.com \ /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: linkBe 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.