linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, david@redhat.com,
	lorenzo.stoakes@oracle.com, baolin.wang@linux.alibaba.com,
	Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
	dev.jain@arm.com, baohua@kernel.org, lance.yang@linux.dev,
	linux-mm@kvack.org, Usama Arif <usamaarif642@gmail.com>,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: [Patch v2] mm/khugepaged: unify pmd folio installation with map_anon_folio_pmd()
Date: Tue, 07 Oct 2025 11:05:13 -0400	[thread overview]
Message-ID: <5A9AC065-0CA2-49F8-9ABA-7238C20F1B06@nvidia.com> (raw)
In-Reply-To: <20251007005022.24413-1-richard.weiyang@gmail.com>

On 6 Oct 2025, at 20:50, 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
> ---
>  include/linux/huge_mm.h |  6 ++++++
>  mm/huge_memory.c        | 14 ++++++++++----
>  mm/khugepaged.c         |  9 +--------
>  3 files changed, 17 insertions(+), 12 deletions(-)

After addressing Lance’s and David’s comments, feel free to add:
Reviewed-by: Zi Yan <ziy@nvidia.com>

Best Regards,
Yan, Zi


      parent reply	other threads:[~2025-10-07 15:05 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
2025-10-08  1:20           ` Wei Yang
2025-10-07  8:53 ` David Hildenbrand
2025-10-07 15:05 ` Zi Yan [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=5A9AC065-0CA2-49F8-9ABA-7238C20F1B06@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --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