From: "Emil Tsalapatis" <emil@etsalapatis.com>
To: "Jiayuan Chen" <jiayuan.chen@linux.dev>, <bpf@vger.kernel.org>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Song Liu" <song@kernel.org>,
"Yonghong Song" <yonghong.song@linux.dev>,
"Jiri Olsa" <jolsa@kernel.org>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"Shuah Khan" <shuah@kernel.org>,
"Woojin Ji" <random6.xyz@gmail.com>,
"Puranjay Mohan" <puranjay@kernel.org>,
"Saket Kumar Bhaskar" <skb99@linux.ibm.com>,
"Ihor Solodrai" <ihor.solodrai@linux.dev>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH bpf-next v2 2/4] bpf: Add memory usage for arena
Date: Fri, 17 Jul 2026 19:33:03 -0400 [thread overview]
Message-ID: <DK18M5FD69A2.2U0WEYWFGIBC0@etsalapatis.com> (raw)
In-Reply-To: <20260717114117.350851-3-jiayuan.chen@linux.dev>
On Fri Jul 17, 2026 at 7:37 AM EDT, Jiayuan Chen wrote:
> arena is the only map type whose map_mem_usage() still returns 0, so
> "bpftool map show" and fdinfo always showed 0 memlock for an arena no
> matter how many pages it had.
>
> Count the pages that are actually mapped into the arena: bump a counter in
> apply_range_set_cb() when a page goes in and drop it in
> apply_range_clear_cb() when a page goes out, both under the arena spinlock.
> map_mem_usage() then just returns nr_pages << PAGE_SHIFT.
>
> Only real data pages are counted, not the scratch page.
>
> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev>
Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
>
> ---
> To sashiko:
> 1. __bpf_alloc_page::can_alloc_pages already check whether we are under lock.
> 2. apply_to_page_range() does not allocate page tables here. arena_map_alloc() already did it.
> ---
> kernel/bpf/arena.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/bpf/arena.c b/kernel/bpf/arena.c
> index 8dbc24460890..f046e878f7ae 100644
> --- a/kernel/bpf/arena.c
> +++ b/kernel/bpf/arena.c
> @@ -55,8 +55,10 @@ struct bpf_arena {
> struct vm_struct *kern_vm;
> struct page *scratch_page;
> struct range_tree rt;
> - /* protects rt */
> + /* protects rt and nr_pages */
> rqspinlock_t spinlock;
> + /* number of pages currently populated in the arena */
> + u64 nr_pages;
> struct list_head vma_list;
> /* protects vma_list */
> struct mutex lock;
> @@ -196,6 +198,7 @@ static int apply_range_set_cb(pte_t *pte, unsigned long addr, void *data)
> set_pte_at(&init_mm, addr, pte, pteval);
> #endif
> d->i++;
> + WRITE_ONCE(d->arena->nr_pages, d->arena->nr_pages + 1);
> return 0;
> }
>
> @@ -231,6 +234,7 @@ static int apply_range_clear_cb(pte_t *pte, unsigned long addr, void *data)
> return 0;
>
> __llist_add(&page->pcp_llist, d->free_pages);
> + WRITE_ONCE(d->arena->nr_pages, d->arena->nr_pages - 1);
> return 0;
> }
>
> @@ -413,7 +417,9 @@ static int arena_map_check_btf(struct bpf_map *map, const struct btf *btf,
>
> static u64 arena_map_mem_usage(const struct bpf_map *map)
> {
> - return 0;
> + struct bpf_arena *arena = container_of(map, struct bpf_arena, map);
> +
> + return (u64)READ_ONCE(arena->nr_pages) << PAGE_SHIFT;
> }
>
> struct vma_list {
next prev parent reply other threads:[~2026-07-17 23:33 UTC|newest]
Thread overview: 9+ 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 [this message]
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 23:36 ` Emil Tsalapatis
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=DK18M5FD69A2.2U0WEYWFGIBC0@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.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