linux-kernel - Re: [PATCH bpf-next v4 0/3] bpf, arm64: use BPF prog pack allocator in BPF JIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <009e49a8-38f0-04cd-2482-f30b84a9069c@iogearbox.net>
Date:   Mon, 3 Jul 2023 19:54:31 +0200
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Mark Rutland <mark.rutland@....com>
Cc:     Puranjay Mohan <puranjay12@...il.com>, ast@...nel.org,
        andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
        catalin.marinas@....com, bpf@...r.kernel.org, kpsingh@...nel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v4 0/3] bpf, arm64: use BPF prog pack allocator
 in BPF JIT

On 7/3/23 7:15 PM, Mark Rutland wrote:
[...]
>> On 6/26/23 10:58 AM, Puranjay Mohan wrote:
>>> BPF programs currently consume a page each on ARM64. For systems with many BPF
>>> programs, this adds significant pressure to instruction TLB. High iTLB pressure
>>> usually causes slow down for the whole system.
>>>
>>> Song Liu introduced the BPF prog pack allocator[1] to mitigate the above issue.
>>> It packs multiple BPF programs into a single huge page. It is currently only
>>> enabled for the x86_64 BPF JIT.
>>>
>>> This patch series enables the BPF prog pack allocator for the ARM64 BPF JIT.
> 
>> If you get a chance to take another look at the v4 changes from Puranjay and
>> in case they look good to you reply with an Ack, that would be great.
> 
> Sure -- this is on my queue of things to look at; it might just take me a few
> days to get the time to give this a proper look.

Awesome, thanks Mark!