linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>,
	 Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	 Brendan Jackman <jackmanb@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>,  Zi Yan <ziy@nvidia.com>,
	David Rientjes <rientjes@google.com>,
	 David Hildenbrand <david@kernel.org>,
	 Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	 "Liam R. Howlett" <Liam.Howlett@oracle.com>,
	 Mike Rapoport <rppt@kernel.org>,
	Joshua Hahn <joshua.hahnjy@gmail.com>,
	 Pedro Falcato <pfalcato@suse.de>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 Vlastimil Babka <vbabka@suse.cz>
Subject: [PATCH RFC v2 0/3] tweaks for __alloc_pages_slowpath()
Date: Fri, 19 Dec 2025 18:38:50 +0100	[thread overview]
Message-ID: <20251219-thp-thisnode-tweak-v2-0-0c01f231fd1c@suse.cz> (raw)

RFC, feel free to ignore until next year... Sending just in case
some feedback will materialize.

Since v1 the main motivating fix (patch 1 of v1) was sent separately:
https://lore.kernel.org/all/20251219-costly-noretry-thisnode-fix-v1-1-e1085a4a0c34@suse.cz/

In patch 2 of v1 I have proposed not to attempt reclaim for costly
__GFP_NORETRY allocations at all. Johannes suggested that we should not
change the semantics that much, so now instead we allow them all (except
with __GFP_THISNODE). The main idea that remains is that we don't decide
based on the exact compaction result anymore.

Patch 3 is a cleanup also based on a suggestion from Johannes, and Patch
4 became the obvious next step in that direction. These should be making
no functional changes.

Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
---
Changes in v2:
- actual THP reclaim fix sent separately
- allow one reclaim attempt for __GFP_NORETRY allocations
- further __alloc_pages_slowpath() cleanups
- Link to v1: https://patch.msgid.link/20251216-thp-thisnode-tweak-v1-0-0e499d13d2eb@suse.cz

---
Vlastimil Babka (3):
      mm/page_alloc: ignore the exact initial compaction result
      mm/page_alloc: refactor the initial compaction handling
      mm/page_alloc: simplify __alloc_pages_slowpath() flow

 mm/page_alloc.c | 169 ++++++++++++++++++++++++++------------------------------
 1 file changed, 77 insertions(+), 92 deletions(-)
---
base-commit: 81a5997c0d5ac4cb3ce65f1128197cb751ccd15b
change-id: 20251216-thp-thisnode-tweak-c9c2acb3a627

Best regards,
-- 
Vlastimil Babka <vbabka@suse.cz>



             reply	other threads:[~2025-12-19 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 17:38 Vlastimil Babka [this message]
2025-12-19 17:38 ` [PATCH RFC v2 1/3] mm/page_alloc: ignore the exact initial compaction result Vlastimil Babka
2025-12-19 17:38 ` [PATCH RFC v2 2/3] mm/page_alloc: refactor the initial compaction handling Vlastimil Babka
2025-12-22  7:40   ` Joshua Hahn
2025-12-19 17:38 ` [PATCH RFC v2 3/3] mm/page_alloc: simplify __alloc_pages_slowpath() flow Vlastimil Babka

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=20251219-thp-thisnode-tweak-v2-0-0c01f231fd1c@suse.cz \
    --to=vbabka@suse.cz \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=jackmanb@google.com \
    --cc=joshua.hahnjy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=pfalcato@suse.de \
    --cc=rientjes@google.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=ziy@nvidia.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