From: Lance Yang <lance.yang@linux.dev>
To: Usama Arif <usama.arif@linux.dev>, Zi Yan <ziy@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
david@kernel.org, chrisl@kernel.org, kasong@tencent.com,
ljs@kernel.org, Linux Memory Management List <linux-mm@kvack.org>,
ying.huang@linux.alibaba.com, Baoquan He <baoquan.he@linux.dev>,
willy@infradead.org, youngjun.park@lge.com, hannes@cmpxchg.org,
riel@surriel.com, shakeel.butt@linux.dev, alex@ghiti.fr,
kas@kernel.org, baohua@kernel.org, dev.jain@arm.com,
baolin.wang@linux.alibaba.com, npache@redhat.com,
"Liam R. Howlett" <liam@infradead.org>,
ryan.roberts@arm.com, Vlastimil Babka <vbabka@kernel.org>,
linux-kernel@vger.kernel.org, nphamcs@gmail.com,
shikemeng@huaweicloud.com, kernel-team@meta.com
Subject: Re: [v2 00/16] mm: PMD-level swap entries for anonymous THPs
Date: Sun, 14 Jun 2026 09:48:30 +0800 [thread overview]
Message-ID: <b08cafbb-a4b7-4609-84ae-dbb2cfcfc8be@linux.dev> (raw)
In-Reply-To: <e68d5c68-9b4e-4959-a507-a9f94f3ce6e0@linux.dev>
On 2026/6/14 03:34, Usama Arif wrote:
>
>
> On 13/06/2026 20:27, Zi Yan wrote:
>> On 9 Jun 2026, at 10:29, Usama Arif wrote:
>>
>>> On 02/06/2026 15:24, Usama Arif wrote:
>>>> When reclaim swaps out a PMD-mapped anonymous THP today, the PMD is
>>>> split into 512 PTE-level swap entries via TTU_SPLIT_HUGE_PMD before
>>>> unmap.
>>>>
>>>> This series introduces a PMD-level swap entry. The huge mapping is
>>>> preserved across the swap round-trip, and do_huge_pmd_swap_page()
>>>> resolves the entire 2 MB region in a single fault on swap-in,
>>>> no khugepaged involvement is needed. swap_map metadata is identical
>>>> either way (512 single-slot counts), so the PTE split buys nothing
>>>> on the swap side, it is purely a page-table representation change.
>>>>
>>>
>>> Hello!
>>>
>>> Just following up if there were any reviews/comments on this series!
>>>
>>> I know its a large series but was just checking if there was any
>>> feedback?
>>
>> Maybe send first 6 clean-up patches separately to get them merged first?
>
> Good idea! Will do that. Thanks!
Yeah, sounds good. Less churn, and the cleanups can land first, and
life is easier for everyone :D
prev parent reply other threads:[~2026-06-14 1:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260602142537.198755-1-usama.arif@linux.dev>
2026-06-09 14:29 ` [v2 00/16] mm: PMD-level swap entries for anonymous THPs Usama Arif
2026-06-10 12:24 ` David Hildenbrand (Arm)
2026-06-10 13:01 ` Lance Yang
2026-06-10 13:48 ` David Hildenbrand (Arm)
2026-06-10 14:44 ` Usama Arif
2026-06-13 4:22 ` Lance Yang
2026-06-13 19:18 ` Usama Arif
2026-06-13 19:27 ` Zi Yan
2026-06-13 19:34 ` Usama Arif
2026-06-13 19:48 ` Usama Arif
2026-06-14 1:48 ` Lance Yang [this message]
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=b08cafbb-a4b7-4609-84ae-dbb2cfcfc8be@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=npache@redhat.com \
--cc=nphamcs@gmail.com \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=youngjun.park@lge.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