From: patchwork-bot+netdevbpf@kernel.org
To: Andrey Grafin <conquistador@yandex-team.ru>
Cc: bpf@vger.kernel.org, andrii@kernel.org
Subject: Re: [PATCH bpf v5 1/2] libbpf: Apply map_set_def_max_entries() for inner_maps on creation
Date: Fri, 19 Jan 2024 21:30:27 +0000 [thread overview]
Message-ID: <170569982709.24319.16024123262665382181.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240117130619.9403-1-conquistador@yandex-team.ru>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 17 Jan 2024 16:06:18 +0300 you wrote:
> This patch allows to auto create BPF_MAP_TYPE_ARRAY_OF_MAPS and
> BPF_MAP_TYPE_HASH_OF_MAPS with values of BPF_MAP_TYPE_PERF_EVENT_ARRAY
> by bpf_object__load().
>
> Previous behaviour created a zero filled btf_map_def for inner maps and
> tried to use it for a map creation but the linux kernel forbids to create
> a BPF_MAP_TYPE_PERF_EVENT_ARRAY map with max_entries=0.
>
> [...]
Here is the summary with links:
- [bpf,v5,1/2] libbpf: Apply map_set_def_max_entries() for inner_maps on creation
https://git.kernel.org/bpf/bpf-next/c/683ed8edd0c7
- [bpf,v5,2/2] selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values
https://git.kernel.org/bpf/bpf-next/c/9d1a26e7e43c
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:[~2024-01-19 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 13:06 [PATCH bpf v5 1/2] libbpf: Apply map_set_def_max_entries() for inner_maps on creation Andrey Grafin
2024-01-17 13:06 ` [PATCH bpf v5 2/2] selftest/bpf: Add map_in_maps with BPF_MAP_TYPE_PERF_EVENT_ARRAY values Andrey Grafin
2024-01-17 16:53 ` Yonghong Song
2024-01-18 1:14 ` Hou Tao
2024-01-17 16:52 ` [PATCH bpf v5 1/2] libbpf: Apply map_set_def_max_entries() for inner_maps on creation Yonghong Song
2024-01-18 1:12 ` Hou Tao
2024-01-19 21:30 ` 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=170569982709.24319.16024123262665382181.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=conquistador@yandex-team.ru \
/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