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 0/2] tweaks for costly order __GFP_NORETRY reclaim
Date: Tue, 16 Dec 2025 16:54:20 +0100	[thread overview]
Message-ID: <20251216-thp-thisnode-tweak-v1-0-0e499d13d2eb@suse.cz> (raw)

This is motivated by an excessive reclaim issue we saw in a customer
workload and was associated with THP page faults and an unexpected
zone_reclaim_mode-like behavior that can happen for those.

The first patch is intended as a minimal targeted backportable fix for
the observed issue. I hope I'll be able to confirm it has fixed the
problem, but it might take some time.

The second patch is a more "let's take a step back and rethink what
we're doing here" so it's separate, as it changes a bit the semantics
of __GFP_NORETRY.

Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
---
Vlastimil Babka (2):
      mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations
      mm, page_alloc: fail costly __GFP_NORETRY allocations faster

 include/linux/gfp_types.h |  2 ++
 mm/page_alloc.c           | 33 +++------------------------------
 2 files changed, 5 insertions(+), 30 deletions(-)
---
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
change-id: 20251216-thp-thisnode-tweak-c9c2acb3a627

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



             reply	other threads:[~2025-12-16 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16 15:54 Vlastimil Babka [this message]
2025-12-16 15:54 ` [PATCH RFC 1/2] mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations Vlastimil Babka
2025-12-16 16:26   ` Michal Hocko
2025-12-16 20:11   ` Johannes Weiner
2025-12-16 20:23   ` Zi Yan
2025-12-17 15:53   ` Pedro Falcato
2025-12-16 15:54 ` [PATCH RFC 2/2] mm, page_alloc: fail costly __GFP_NORETRY allocations faster Vlastimil Babka
2025-12-16 16:28   ` Michal Hocko
2025-12-16 20:32   ` Johannes Weiner
2025-12-17  8:46     ` Vlastimil Babka
2025-12-17 16:35       ` Johannes Weiner

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=20251216-thp-thisnode-tweak-v1-0-0e499d13d2eb@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