Re: [PATCH bpf-next v2 0/3] Use kmalloc_nolock() universally in BPF local storage

patchwork-bot+netdevbpf
2026-04-11T04:30:36Z

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 10 Apr 2026 18:54:15 -0700 you wrote:
> Socket local storage did not convert to use kmalloc_nolock() since there
> were observable performance degredation due to kfree_nolock() hitting the
> slow path and the lack of kfree_rcu()-like batching freeing. Now that
> these concern were addressed in slub, convert all remaining local storage
> flavors to use kmalloc_nolock().
>
> v1 -> v2:
> - Fix build (CI, Alexei)
>
> [...]

Here is the summary with links:
- [bpf-next,v2,1/3] selftests/bpf: Remove kmalloc tracing from local storage create bench
https://git.kernel.org/bpf/bpf-next/c/78ee02a966ad
- [bpf-next,v2,2/3] bpf: Use kmalloc_nolock() universally in local storage
https://git.kernel.org/bpf/bpf-next/c/5063e7758899
- [bpf-next,v2,3/3] bpf: Remove gfp_flags plumbing from bpf_local_storage_update()
https://git.kernel.org/bpf/bpf-next/c/136deea435dc

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.