Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@xxxxxxxxxx>:
On Thu, 21 Dec 2023 19:17:29 -0800 you wrote:
> Currently when a bpf program intends to allocate memory for percpu kptr,
> the verifier will call bpf_mem_alloc_init() to prefill all supported
> unit sizes and this caused memory consumption very big for large number
> of cpus. For example, for 128-cpu system, the total memory consumption
> with initial prefill is ~175MB. Things will become worse for systems
> with even more cpus.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/8] bpf: Avoid unnecessary extra percpu memory allocation
https://git.kernel.org/bpf/bpf-next/c/9beda16c257d
- [bpf-next,v6,2/8] bpf: Add objcg to bpf_mem_alloc
https://git.kernel.org/bpf/bpf-next/c/9fc8e802048a
- [bpf-next,v6,3/8] bpf: Allow per unit prefill for non-fix-size percpu memory allocator
https://git.kernel.org/bpf/bpf-next/c/c39aa3b289e9
- [bpf-next,v6,4/8] bpf: Refill only one percpu element in memalloc
https://git.kernel.org/bpf/bpf-next/c/5b95e638f134
- [bpf-next,v6,5/8] bpf: Use smaller low/high marks for percpu allocation
https://git.kernel.org/bpf/bpf-next/c/0e2ba9f96f9b
- [bpf-next,v6,6/8] bpf: Limit up to 512 bytes for bpf_global_percpu_ma allocation
https://git.kernel.org/bpf/bpf-next/c/5c1a37653260
- [bpf-next,v6,7/8] selftests/bpf: Cope with 512 bytes limit with bpf_global_percpu_ma
https://git.kernel.org/bpf/bpf-next/c/21f5a801c171
- [bpf-next,v6,8/8] selftests/bpf: Add a selftest with > 512-byte percpu allocation size
https://git.kernel.org/bpf/bpf-next/c/adc8c4549d9e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
