From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Lorenz Bauer <lmb@cloudflare.com>
Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Luke Nelson <luke.r.nels@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
kernel-team <kernel-team@cloudflare.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] Fix up bpf_jit_limit some more
Date: Wed, 20 Oct 2021 18:22:24 -0700 [thread overview]
Message-ID: <CAADnVQJRUz81YeBqM-Kk4OM7FXAw07TNA_mOY1ZGAZ5MHpsE2A@mail.gmail.com> (raw)
In-Reply-To: <20211014142554.53120-1-lmb@cloudflare.com>
On Thu, Oct 14, 2021 at 7:26 AM Lorenz Bauer <lmb@cloudflare.com> wrote:
>
> Fix some inconsistencies of bpf_jit_limit on non-x86 platforms.
> I've dropped exposing bpf_jit_current since we couldn't agree on
> file modes, correct names, etc.
Applied to bpf tree. Seems more appropriate there.
prev parent reply other threads:[~2021-10-21 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:25 [PATCH v3 0/3] Fix up bpf_jit_limit some more Lorenz Bauer
2021-10-14 14:25 ` [PATCH v3 1/3] bpf: define bpf_jit_alloc_exec_limit for riscv JIT Lorenz Bauer
2021-10-18 6:14 ` Björn Töpel
2021-10-14 14:25 ` [PATCH v3 2/3] bpf: define bpf_jit_alloc_exec_limit for arm64 JIT Lorenz Bauer
2021-10-14 14:25 ` [PATCH v3 3/3] bpf: prevent increasing bpf_jit_limit above max Lorenz Bauer
2021-10-21 1:22 ` Alexei Starovoitov [this message]
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=CAADnVQJRUz81YeBqM-Kk4OM7FXAw07TNA_mOY1ZGAZ5MHpsE2A@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@cloudflare.com \
--cc=linux-riscv@lists.infradead.org \
--cc=lmb@cloudflare.com \
--cc=luke.r.nels@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@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: 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;
as well as URLs for NNTP newsgroup(s).