From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, David Hildenbrand <david@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>, Zi Yan <ziy@nvidia.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH v2 0/5] mm: mincore: misc cleanups
Date: Fri, 10 Jul 2026 20:00:46 +0800 [thread overview]
Message-ID: <20260710120052.103886-1-wangkefeng.wang@huawei.com> (raw)
This series cleans up and simplifies the mincore. Most importantly,
it removes the historical special handling for VM_PFNMAP mappings,
reporting them as resident memory instead of always being non-resident
memory.
v2:
- Separate per-VMA lock changes as suggested by Pedro, it should be
based on the new API [1], will resend once new API out.
- Check VM_PFNMAP explicitly in can_do_mincore() to avoid trigger a
split in the page table walk, found in sashiko[[2]
- Replace GFP_USER with GFP_KERNEL, suggested by Andrew
- Add Pedro RB and mincore_page() refactor patch
[1] https://lore.kernel.org/linux-mm/20260610230415.C0521C88@davehans-spike.ostc.intel.com/
[2] https://sashiko.dev/#/patchset/20260701144047.3786939-1-wangkefeng.wang%40huawei.com?part=2
Kefeng Wang (5):
mm: mincore: remove special handling for VM_PFNMAP
mm: mincore: replace __get_free_page() with kmalloc()
mm: mincore: remove xa_is_value() in mincore_swap()
mm: mincore: improve mincore_hugetlb()
mm: mincore: refactor mincore_page()
mm/mincore.c | 66 ++++++++++++++++++----------------------------------
1 file changed, 22 insertions(+), 44 deletions(-)
--
2.55.0
next reply other threads:[~2026-07-10 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 12:00 Kefeng Wang [this message]
2026-07-10 12:00 ` [PATCH v2 1/5] mm: mincore: remove special handling for VM_PFNMAP Kefeng Wang
2026-07-10 12:07 ` David Hildenbrand (Arm)
2026-07-10 12:00 ` [PATCH v2 2/5] mm: mincore: replace __get_free_page() with kmalloc() Kefeng Wang
2026-07-10 12:09 ` David Hildenbrand (Arm)
2026-07-10 12:00 ` [PATCH v2 3/5] mm: mincore: remove xa_is_value() in mincore_swap() Kefeng Wang
2026-07-10 12:09 ` David Hildenbrand (Arm)
2026-07-10 12:00 ` [PATCH v2 4/5] mm: mincore: improve mincore_hugetlb() Kefeng Wang
2026-07-10 12:17 ` David Hildenbrand (Arm)
2026-07-10 12:00 ` [PATCH v2 5/5] mm: mincore: refactor mincore_page() Kefeng Wang
2026-07-10 12:19 ` David Hildenbrand (Arm)
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=20260710120052.103886-1-wangkefeng.wang@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=vbabka@kernel.org \
--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