From: patchwork-bot+netdevbpf@kernel.org
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, daniel@iogearbox.net,
harry@kernel.org
Subject: Re: [PATCH bpf-next v5 0/9] bpf libarena allocator improvements
Date: Thu, 12 Nov 2026 21:00:10 +0000 [thread overview]
Message-ID: <179451721077.643214.10911738929932344847.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110003838.8739-1-emil@etsalapatis.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 10 Nov 2026 00:38:29 +0000 you wrote:
> The libarena buddy allocator's design has up until now prioritized
> ease of verification. With new verifier features like unlimited
> global stack frames and a large stack size we can now improve
> the allocator's performance and robustness.
>
> This patch introduces per-CPU caches for the allocator. The overall
> caching design is inspired by tcmalloc. Each CPU has its own static
> object LIFOs, one for each allocator order. This speeds up allocation
> and freeing for BPF programs that have some degree of locality. The
> CPU caches are lockless. The caches are replenished from and spilled
> into "transfer caches", per-order caches shared between the CPUs that
> amortize the cost of spilling/refilling. Data from the transfer caches
> is in turn moved from and to the allocator.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/9] selftests/bpf: libarena: Add bulk buddy allocation helpers
https://git.kernel.org/bpf/bpf-next/c/d8276c0d08cc
- [bpf-next,v5,2/9] selftests/bpf: Add a parallel buddy allocator benchmark
https://git.kernel.org/bpf/bpf-next/c/4d71673bc4b5
- [bpf-next,v5,3/9] selftests/bpf: libarena: Make spinlock trylock match arena_spin_unlock
https://git.kernel.org/bpf/bpf-next/c/b77e7e9c49fd
- [bpf-next,v5,4/9] selftests/bpf: libarena: Raise arena spinlock CPU limits
https://git.kernel.org/bpf/bpf-next/c/27f2cf406a35
- [bpf-next,v5,5/9] selftests/bpf: libarena: Add buddy per-CPU caches
https://git.kernel.org/bpf/bpf-next/c/c8d21d25241b
- [bpf-next,v5,6/9] selftests/bpf: libarena: Handle NMI reentrancy
https://git.kernel.org/bpf/bpf-next/c/633635ab8d51
- [bpf-next,v5,7/9] selftests/bpf: libarena: Refill local caches in batches
https://git.kernel.org/bpf/bpf-next/c/e5728f923b03
- [bpf-next,v5,8/9] selftests/bpf: libarena: Add a transfer cache
https://git.kernel.org/bpf/bpf-next/c/be73f5c9f9d3
- [bpf-next,v5,9/9] selftests/bpf: libarena: Cover buddy cache fast paths
https://git.kernel.org/bpf/bpf-next/c/ed5558fb22a3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-12 21:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 0:38 [PATCH bpf-next v5 0/9] bpf libarena allocator improvements Emil Tsalapatis
2026-11-10 0:38 ` [PATCH bpf-next v5 1/9] selftests/bpf: libarena: Add bulk buddy allocation helpers Emil Tsalapatis
2026-11-10 0:38 ` [PATCH bpf-next v5 2/9] selftests/bpf: Add a parallel buddy allocator benchmark Emil Tsalapatis
2026-11-10 4:51 ` bot+bpf-ci
2026-11-10 0:38 ` [PATCH bpf-next v5 3/9] selftests/bpf: libarena: Make spinlock trylock match arena_spin_unlock Emil Tsalapatis
2026-11-10 0:38 ` [PATCH bpf-next v5 4/9] selftests/bpf: libarena: Raise arena spinlock CPU limits Emil Tsalapatis
2026-11-10 0:38 ` [PATCH bpf-next v5 5/9] selftests/bpf: libarena: Add buddy per-CPU caches Emil Tsalapatis
2026-11-10 0:38 ` [PATCH bpf-next v5 6/9] selftests/bpf: libarena: Handle NMI reentrancy Emil Tsalapatis
2026-11-10 1:34 ` sashiko-bot
2026-11-10 4:51 ` bot+bpf-ci
2026-11-10 0:38 ` [PATCH bpf-next v5 7/9] selftests/bpf: libarena: Refill local caches in batches Emil Tsalapatis
2026-11-10 4:51 ` bot+bpf-ci
2026-11-10 0:38 ` [PATCH bpf-next v5 8/9] selftests/bpf: libarena: Add a transfer cache Emil Tsalapatis
2026-11-10 0:38 ` [PATCH bpf-next v5 9/9] selftests/bpf: libarena: Cover buddy cache fast paths Emil Tsalapatis
2026-11-12 21:00 ` patchwork-bot+netdevbpf [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=179451721077.643214.10911738929932344847.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=harry@kernel.org \
--cc=memxor@gmail.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