From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Andrea Righi" <arighi@nvidia.com>
Cc: "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>,
"Ihor Solodrai" <ihor.solodrai@linux.dev>,
"John Fastabend" <john.fastabend@gmail.com>,
"Josh Don" <joshdon@google.com>,
"Vineeth Pillai" <vineethrp@google.com>,
"Balbir Singh" <balbirs@nvidia.com>,
"Shameer Kolothum" <skolothumtho@nvidia.com>,
"Himadri Chhaya-Shailesh" <himadrics@protonmail.com>,
"NchangRoy" <royfru44@gmail.com>, <bpf@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf-next 0/5] bpf: Expose pinned arenas as sized bpffs files
Date: Mon, 19 Oct 2026 19:32:33 +0000 [thread overview]
Message-ID: <DM92D7YEU0AE.2XRZH7RV2US4@gmail.com> (raw)
In-Reply-To: <atXYdpDukXObjE69@gpd4>
On Mon, Oct 19, 2026 at 01:44 AM Andrea Righi <arighi@nvidia.com> wrote:
> That's fine for a single long-running guest, but with VMs coming and
> going the host arena would only grow (this was also Josh's concern about
> the high watermark). Would it be ok with an explicit release of an
> imported range (clear the ptes, flush, set rt_own back, unpin the
> folios)? A BPF prog touching a released range would then hit the usual
> arena fault handling, like any unallocated page.
make sense to me.
In my prototype arena_free_pages() sees the imported range in rt_own.
Instead of returning early it can do the above and
give the range back to rt.
prev parent reply other threads:[~2026-10-19 19:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 22:45 Andrea Righi
2026-10-10 22:45 ` [PATCH 1/5] bpf: Add an arena flag to retain allocated pages Andrea Righi
2026-10-10 22:45 ` [PATCH 2/5] bpf: Expose pinned arenas as sized bpffs files Andrea Righi
2026-10-10 23:40 ` bot+bpf-ci
2026-10-10 22:45 ` [PATCH 3/5] docs/bpf: Document pinned arena file mappings Andrea Righi
2026-10-10 23:19 ` bot+bpf-ci
2026-10-10 22:45 ` [PATCH 4/5] selftests/bpf: Test " Andrea Righi
2026-10-10 23:40 ` bot+bpf-ci
2026-10-10 22:46 ` [PATCH 5/5] selftests/bpf: Test two-way arena access with two guests Andrea Righi
2026-10-10 23:40 ` bot+bpf-ci
2026-10-15 17:50 ` [PATCH bpf-next 0/5] bpf: Expose pinned arenas as sized bpffs files Josh Don
2026-10-19 8:17 ` Andrea Righi
2026-10-16 19:03 ` Alexei Starovoitov
2026-10-16 19:52 ` Andrii Nakryiko
2026-10-18 0:52 ` Alexei Starovoitov
2026-10-19 8:49 ` Andrea Righi
2026-10-19 16:19 ` Andrii Nakryiko
2026-10-19 16:58 ` Alexei Starovoitov
2026-10-19 8:44 ` Andrea Righi
2026-10-19 19:32 ` Alexei Starovoitov [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=DM92D7YEU0AE.2XRZH7RV2US4@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=arighi@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=himadrics@protonmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=joshdon@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=royfru44@gmail.com \
--cc=skolothumtho@nvidia.com \
--cc=song@kernel.org \
--cc=vineethrp@google.com \
--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
all inboxes | Powered by JetHome®