Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@xxxxxxxxxx>:
On Tue, 23 May 2023 17:45:35 -0700 you wrote:
> Due to the way the datasec maps like bss, data, rodata are memory
> mapped, they cannot be resized with bpf_map__set_value_size() like
> non-datasec maps can. This series offers a way to allow the resizing of
> datasec maps, by having the mapped regions resized as needed and also
> adjusting associated BTF info if possible.
>
> The thought behind this is to allow for use cases where a given datasec
> needs to scale to for example the number of CPU's present. A bpf program
> can have a global array in a data section with an initial length and
> before loading the bpf program, the array length could be extended to
> match the CPU count. The selftests included in this series perform this
> scaling to an arbitrary value to demonstrate how it can work.
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/2] libbpf: add capability for resizing datasec maps
https://git.kernel.org/bpf/bpf-next/c/9d0a23313b1a
- [v3,bpf-next,2/2] libbpf: selftests for resizing datasec maps
https://git.kernel.org/bpf/bpf-next/c/08b089567573
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
