From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Emil Tsalapatis" <emil@etsalapatis.com>, <bpf@vger.kernel.org>
Cc: <andrii@kernel.org>, <eddyz87@gmail.com>, <memxor@gmail.com>,
<daniel@iogearbox.net>
Subject: Re: [PATCH bpf v3 3/7] bpf: Add sleepable arena page allocation path
Date: Sat, 26 Sep 2026 07:47:43 +0000 [thread overview]
Message-ID: <DLP2Z120OC61.TTRUEZ9MMG5K@gmail.com> (raw)
In-Reply-To: <DLOQESM8SNGA.2ASMGV6KHJ4WB@etsalapatis.com>
On Fri, Sep 25, 2026 at 09:57 PM Emil Tsalapatis <emil@etsalapatis.com> wrote:
> The nr_pages_in_flight is there for the edge case where multiple concurrent
> allocations in the arena inflate memcg usage close to the limit, then a non-arena
> related allocation fails/triggers OOM. If we're fine with that happy to remove
> it since it's a bit of a tacked-on hack.
Yes. Let's remove it.
An arena that is populated up to the memcg limit does the same
to other allocations in that memcg.
> I'll replace it with __GFP_RETRY_MAYFAIL on alloc_pages() so that the allocation
> doesn't accidentally trigger the OOM killer. AFAICT it can do so otherwise.
confused...
Patch 2 already adds __GFP_RETRY_MAYFAIL to bpf_alloc_page().
next prev parent reply other threads:[~2026-09-26 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 20:39 [PATCH bpf v3 0/7] Make sleepable arena paths use sleepable alloc_pages Emil Tsalapatis
2026-09-25 20:39 ` [PATCH bpf v3 1/7] bpf: Use an llist for page allocations Emil Tsalapatis
2026-09-25 20:39 ` [PATCH bpf v3 2/7] bpf: Add sleepable argument to bpf_alloc_pages() Emil Tsalapatis
2026-09-25 20:39 ` [PATCH bpf v3 3/7] bpf: Add sleepable arena page allocation path Emil Tsalapatis
2026-09-25 21:25 ` Alexei Starovoitov
2026-09-25 21:57 ` Emil Tsalapatis
2026-09-26 7:47 ` Alexei Starovoitov [this message]
2026-09-25 20:39 ` [PATCH bpf v3 4/7] selftests/bpf: Test large allocations for both sleepable/nonsleepable arena users Emil Tsalapatis
2026-09-25 20:39 ` [PATCH bpf v3 5/7] bpf: Support call-site kfunc specialization for near calls Emil Tsalapatis
2026-09-25 20:39 ` [PATCH bpf v3 6/7] bpf: Support call-site kfunc specialization for far calls Emil Tsalapatis
2026-09-25 20:39 ` [PATCH bpf v3 7/7] selftests/bpf: Test per-call site function specialization 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=DLP2Z120OC61.TTRUEZ9MMG5K@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=memxor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.