From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Qi Zheng <qi.zheng@linux.dev>
Subject: [PATCH v1 0/2] mm: move pte table reclaim code to memory.c
Date: Mon, 19 Jan 2026 23:07:06 +0100 [thread overview]
Message-ID: <20260119220708.3438514-1-david@kernel.org> (raw)
Some cleanups for PT table reclaim code, triggered by a false-positive
warning we might start to see soon after we unlocked pt-reclaim on
architectures besides x86-64.
Cross compiled on plenty of architectures, tested on x86-64 with
a simple test case that allocates plenty of page tables in a sparse
memory area to see if they will get reclaimed.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@kernel.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: Vlastimil Babka <vbabka@suse.cz>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Qi Zheng <qi.zheng@linux.dev>
David Hildenbrand (Red Hat) (2):
mm: move pte table reclaim code to memory.c
mm/memory: handle non-split locks correctly in zap_empty_pte_table()
MAINTAINERS | 1 -
mm/Makefile | 1 -
mm/internal.h | 18 -------------
mm/memory.c | 70 ++++++++++++++++++++++++++++++++++++++++++-----
mm/pt_reclaim.c | 72 -------------------------------------------------
5 files changed, 64 insertions(+), 98 deletions(-)
delete mode 100644 mm/pt_reclaim.c
base-commit: ac1303686c1e823c9c88b20c5f8587629ad94a11
--
2.52.0
next reply other threads:[~2026-01-19 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 22:07 David Hildenbrand (Red Hat) [this message]
2026-01-19 22:07 ` [PATCH v1 1/2] " David Hildenbrand (Red Hat)
2026-01-20 3:30 ` Qi Zheng
2026-01-20 11:19 ` Kiryl Shutsemau
2026-01-21 12:08 ` David Hildenbrand (Red Hat)
2026-01-19 22:07 ` [PATCH v1 2/2] mm/memory: handle non-split locks correctly in zap_empty_pte_table() David Hildenbrand (Red Hat)
2026-01-20 3:32 ` Qi Zheng
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=20260119220708.3438514-1-david@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=qi.zheng@linux.dev \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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