From: patchwork-bot+netdevbpf@kernel.org
To: JP Kobryn <inwardvessel@gmail.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v3 bpf-next 0/2] libbpf: capability for resizing datasec maps
Date: Wed, 24 May 2023 18:50:20 +0000 [thread overview]
Message-ID: <168495422096.11839.5514267054305588279.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230524004537.18614-1-inwardvessel@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
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
prev parent reply other threads:[~2023-05-24 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 0:45 [PATCH v3 bpf-next 0/2] libbpf: capability for resizing datasec maps JP Kobryn
2023-05-24 0:45 ` [PATCH v3 bpf-next 1/2] libbpf: add " JP Kobryn
2023-05-24 0:45 ` [PATCH v3 bpf-next 2/2] libbpf: selftests " JP Kobryn
2023-05-24 18:48 ` [PATCH v3 bpf-next 0/2] libbpf: capability " Andrii Nakryiko
2023-05-24 18:50 ` 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=168495422096.11839.5514267054305588279.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=inwardvessel@gmail.com \
--cc=kernel-team@meta.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;
as well as URLs for NNTP newsgroup(s).