From: Zi Yan <ziy@nvidia.com>
To: Dev Jain <dev.jain@arm.com>
Cc: Lance Yang <lance.yang@linux.dev>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-mm@kvack.org, Usama Arif <usamaarif642@gmail.com>,
baolin.wang@linux.alibaba.com,
Matthew Wilcox <willy@infradead.org>,
david@redhat.com, lorenzo.stoakes@oracle.com,
ryan.roberts@arm.com, npache@redhat.com, baohua@kernel.org,
Liam.Howlett@oracle.com, akpm@linux-foundation.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: Re: [Patch v2] mm/khugepaged: unify pmd folio installation with map_anon_folio_pmd()
Date: Tue, 07 Oct 2025 10:59:33 -0400 [thread overview]
Message-ID: <69B96963-AA57-4042-B00E-59260CB2514F@nvidia.com> (raw)
In-Reply-To: <b2a474e3-58a0-45f1-8015-46b30c2d0660@arm.com>
On 7 Oct 2025, at 9:11, Dev Jain wrote:
> On 07/10/25 5:54 pm, Lance Yang wrote:
>>
>>
>> On 2025/10/7 17:54, Dev Jain wrote:
>>>
>>> On 07/10/25 9:36 am, Anshuman Khandual wrote:
>>>>
>>>> On 07/10/25 6:20 AM, Wei Yang wrote:
>>>>> Currently we install pmd folio with map_anon_folio_pmd() in
>>>>> __do_huge_pmd_anonymous_page() and do_huge_zero_wp_pmd(). While in
>>>>> collapse_huge_page(), it is done with identical code except statistics
>>>>> adjustment.
>>>>>
>>>>> Unify the process with map_anon_folio_pmd() to install pmd folio. Split
>>>>> it to map_anon_folio_pmd_pf() and map_anon_folio_pmd_nopf() to be used
>>>>> in page fault or not respectively.
>>>>>
>>>>> No functional change is intended.
>>>>>
>>>>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>>>>> Cc: David Hildenbrand <david@redhat.com>
>>>>> Cc: Lance Yang <lance.yang@linux.dev>
>>>>> Cc: Dev Jain <dev.jain@arm.com>
>>>>> Cc: Zi Yan <ziy@nvidia.com>
>>>>> Cc: Usama Arif <usamaarif642@gmail.com>
>>>>> Cc: Matthew Wilcox <willy@infradead.org>
>>>>>
>>>>> ---
>>>>> v2:
>>>>> * split to map_anon_folio_pmd_[no]pf() suggested by Matthew
>>>> On which branch this patch applies against ?
>>>
>>> +1, does not apply on mm-new for me. There have been multiple patches
>>> changing the same file so it will be beneficial to say what commit
>>> it applies against.
>>
>> I think this patch applies on top of the patch[1], which is based on mm-new.
>>
>> [1] https://lore.kernel.org/linux-mm/20251002013825.20448-1-richard.weiyang@gmail.com
>
> Thanks, but this is not yet in mm-new. There are some unaddressed comments there.
>
> Wei, please resend this patch based on mm-new. I would urge you to hold off sending
>
> multiple patches all of which change the same file and have close dependency, till the
>
> first one gets merged.
Or just send both patches in a series to show the dependency. That makes
reviewers’ lives much easier.
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-10-07 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 0:50 Wei Yang
2025-10-07 1:16 ` Lance Yang
2025-10-07 4:06 ` Anshuman Khandual
2025-10-07 9:54 ` Dev Jain
2025-10-07 12:24 ` Lance Yang
2025-10-07 13:11 ` Dev Jain
2025-10-07 14:59 ` Zi Yan [this message]
2025-10-08 1:20 ` Wei Yang
2025-10-07 8:53 ` David Hildenbrand
2025-10-07 15:05 ` Zi Yan
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=69B96963-AA57-4042-B00E-59260CB2514F@nvidia.com \
--to=ziy@nvidia.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=usamaarif642@gmail.com \
--cc=willy@infradead.org \
/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