From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, shuah@kernel.org,
random6.xyz@gmail.com, puranjay@kernel.org, skb99@linux.ibm.com,
ihor.solodrai@linux.dev, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/4] bpf: Add memory usage for arena and selftest
Date: Sun, 19 Jul 2026 16:20:12 +0000 [thread overview]
Message-ID: <178447801214.2765968.4502308683135798549.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260717114117.350851-1-jiayuan.chen@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Fri, 17 Jul 2026 19:37:00 +0800 you wrote:
> arena is the only map type whose map_mem_usage() still returns 0, so
> bpftool and fdinfo always show 0 memlock for it no matter how many pages
> it holds. This series adds the accounting, runs the arena selftests
> serially so they don't OOM a small CI VM, and adds a test for it.
>
> v1 -> v2:
> - split the scratch_page -> arena refactor into a prep patch (no
> functional change)
> - use WRITE_ONCE() for nr_pages to pair with the lockless reader
> - reword the "run serially" commit message
> - selftest: alloc prog returns 0 so the failure check is reached
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/4] bpf: Pass arena instead of scratch_page to the pte callbacks
https://git.kernel.org/bpf/bpf-next/c/f8248ac8f044
- [bpf-next,v2,2/4] bpf: Add memory usage for arena
https://git.kernel.org/bpf/bpf-next/c/89318afb1414
- [bpf-next,v2,3/4] selftests/bpf: Run arena tests serially
https://git.kernel.org/bpf/bpf-next/c/a14f9ba080c1
- [bpf-next,v2,4/4] selftests/bpf: Add tests for memory usage for arena
https://git.kernel.org/bpf/bpf-next/c/29e4bcf12604
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:[~2026-07-19 16:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 11:37 [PATCH bpf-next v2 0/4] bpf: Add memory usage for arena and selftest Jiayuan Chen
2026-07-17 11:37 ` [PATCH bpf-next v2 1/4] bpf: Pass arena instead of scratch_page to the pte callbacks Jiayuan Chen
2026-07-17 23:32 ` Emil Tsalapatis
2026-07-17 11:37 ` [PATCH bpf-next v2 2/4] bpf: Add memory usage for arena Jiayuan Chen
2026-07-17 23:33 ` Emil Tsalapatis
2026-07-17 11:37 ` [PATCH bpf-next v2 3/4] selftests/bpf: Run arena tests serially Jiayuan Chen
2026-07-17 23:34 ` Emil Tsalapatis
2026-07-17 11:37 ` [PATCH bpf-next v2 4/4] selftests/bpf: Add tests for memory usage for arena Jiayuan Chen
2026-07-17 11:53 ` sashiko-bot
2026-07-17 13:18 ` Jiayuan Chen
2026-07-17 23:36 ` Emil Tsalapatis
2026-07-19 16:20 ` 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=178447801214.2765968.4502308683135798549.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jiayuan.chen@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
--cc=random6.xyz@gmail.com \
--cc=shuah@kernel.org \
--cc=skb99@linux.ibm.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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