[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAADnVQJRUz81YeBqM-Kk4OM7FXAw07TNA_mOY1ZGAZ5MHpsE2A@mail.gmail.com>
Date: Wed, 20 Oct 2021 18:22:24 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Lorenz Bauer <lmb@...udflare.com>
Cc: Nicolas Dichtel <nicolas.dichtel@...nd.com>,
Luke Nelson <luke.r.nels@...il.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
kernel-team <kernel-team@...udflare.com>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Network Development <netdev@...r.kernel.org>,
bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH v3 0/3] Fix up bpf_jit_limit some more
On Thu, Oct 14, 2021 at 7:26 AM Lorenz Bauer <lmb@...udflare.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.
Powered by blists - more mailing lists