From: Wupeng Ma <mawupeng1@huawei.com>
To: <akpm@linux-foundation.org>, <vbabka@suse.cz>
Cc: <surenb@google.com>, <jackmanb@google.com>, <hannes@cmpxchg.org>,
<ziy@nvidia.com>, <wangkefeng.wang@huawei.com>,
<mawupeng1@huawei.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: [RFC PATCH] mm: Drain PCP during direct reclaim
Date: Fri, 6 Jun 2025 14:59:30 +0800 [thread overview]
Message-ID: <20250606065930.3535912-1-mawupeng1@huawei.com> (raw)
Memory retained in Per-CPU Pages (PCP) caches can prevent hugepage
allocations from succeeding despite sufficient free system memory. This
occurs because:
1. Hugepage allocations don't actively trigger PCP draining
2. Direct reclaim path fails to trigger drain_all_pages() when:
a) All zone pages are free/hugetlb (!did_some_progress)
b) Compaction skips due to costly order watermarks (COMPACT_SKIPPED)
Reproduction:
- Alloc page and free the page via put_page to release to pcp
- Observe hugepage reservation failure
Solution:
Actively drain PCP during direct reclaim for memory allocations.
This increases page allocation success rate by making stranded pages
available to any order allocations.
Verification:
This issue can be reproduce easily in zone movable with the following
step:
w/o this patch
# numactl -m 2 dd if=/dev/urandom of=/dev/shm/testfile bs=4k count=64
# rm -f /dev/shm/testfile
# sync
# echo 3 > /proc/sys/vm/drop_caches
# echo 2048 > /sys/devices/system/node/node2/hugepages/hugepages-2048kB/nr_hugepages
# cat /sys/devices/system/node/node2/hugepages/hugepages-2048kB/nr_hugepages
2029
w/ this patch
# numactl -m 2 dd if=/dev/urandom of=/dev/shm/testfile bs=4k count=64
# rm -f /dev/shm/testfile
# sync
# echo 3 > /proc/sys/vm/drop_caches
# echo 2048 > /sys/devices/system/node/node2/hugepages/hugepages-2048kB/nr_hugepages
# cat /sys/devices/system/node/node2/hugepages/hugepages-2048kB/nr_hugepages
2047
Signed-off-by: Wupeng Ma <mawupeng1@huawei.com>
---
mm/page_alloc.c | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 2ef3c07266b3..464f2e48651e 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -4137,28 +4137,22 @@ __alloc_pages_direct_reclaim(gfp_t gfp_mask, unsigned int order,
{
struct page *page = NULL;
unsigned long pflags;
- bool drained = false;
psi_memstall_enter(&pflags);
*did_some_progress = __perform_reclaim(gfp_mask, order, ac);
- if (unlikely(!(*did_some_progress)))
- goto out;
-
-retry:
- page = get_page_from_freelist(gfp_mask, order, alloc_flags, ac);
+ if (likely(*did_some_progress))
+ page = get_page_from_freelist(gfp_mask, order, alloc_flags, ac);
/*
* If an allocation failed after direct reclaim, it could be because
* pages are pinned on the per-cpu lists or in high alloc reserves.
* Shrink them and try again
*/
- if (!page && !drained) {
+ if (!page) {
unreserve_highatomic_pageblock(ac, false);
drain_all_pages(NULL);
- drained = true;
- goto retry;
+ page = get_page_from_freelist(gfp_mask, order, alloc_flags, ac);
}
-out:
psi_memstall_leave(&pflags);
return page;
--
2.43.0
next reply other threads:[~2025-06-06 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 6:59 Wupeng Ma [this message]
2025-06-06 11:19 ` Johannes Weiner
2025-06-10 9:18 ` mawupeng
2025-06-11 7:55 ` Raghavendra K T
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=20250606065930.3535912-1-mawupeng1@huawei.com \
--to=mawupeng1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.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