From: Christoph Hellwig <hch@infradead.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Mikulas Patocka <mpatocka@redhat.com>,
"Vishal Moola (Oracle)" <vishal.moola@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
zkabelac@redhat.com, Matthew Sakai <msakai@redhat.com>,
linux-mm@kvack.org, dm-devel@lists.linux.dev
Subject: Re: [PATCH] mm: allow __GFP_RETRY_MAYFAIL in vmalloc
Date: Tue, 24 Feb 2026 06:03:13 -0800 [thread overview]
Message-ID: <aZ2voRA5VJytcfLp@infradead.org> (raw)
In-Reply-To: <aZ2YDD_l5JN78DJC@tiehlicka>
On Tue, Feb 24, 2026 at 01:22:36PM +0100, Michal Hocko wrote:
> One thing that we could do to improve __GFP_RETRY_MAYFAIL resp.
> __GFP_NORETRY is to use NOWAIT allocation semantic for page table
> allocations as those could be achieved by scoped allocation context.
> This could cause pre-mature failure after the whole bunch of memory has
> already been allocated for the backing pages but considering that page
> table allocations should be more and more rare over system runtime it
> might be just a reasonable workaround. WDYT?
Why bother? __GFP_RETRY_MAYFAIL has pretty lose semantics. Trying
too hard to allocate PTEs is not breaking the overall concept.
next prev parent reply other threads:[~2026-02-24 14:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 16:33 Mikulas Patocka
2026-02-21 1:19 ` SeongJae Park
2026-02-23 5:48 ` Anshuman Khandual
2026-02-23 19:02 ` Vishal Moola (Oracle)
2026-02-23 19:25 ` Mikulas Patocka
2026-02-23 20:07 ` Uladzislau Rezki
2026-02-23 22:08 ` Michal Hocko
2026-02-24 11:39 ` Uladzislau Rezki
2026-02-24 12:22 ` Michal Hocko
2026-02-24 14:03 ` Christoph Hellwig [this message]
2026-02-24 14:22 ` Shakeel Butt
2026-02-24 14:26 ` Christoph Hellwig
2026-02-24 14:34 ` Michal Hocko
2026-02-24 15:38 ` Uladzislau Rezki
2026-02-24 15:44 ` Michal Hocko
2026-02-24 15:51 ` Michal Hocko
2026-02-24 16:07 ` Uladzislau Rezki
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=aZ2voRA5VJytcfLp@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mpatocka@redhat.com \
--cc=msakai@redhat.com \
--cc=sj@kernel.org \
--cc=urezki@gmail.com \
--cc=vishal.moola@gmail.com \
--cc=zkabelac@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox