linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: akpm@linux-foundation.org, david@redhat.com,
	lorenzo.stoakes@oracle.com, ziy@nvidia.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
Cc: linux-mm@kvack.org, Wei Yang <richard.weiyang@gmail.com>
Subject: [Patch v3 0/4] mm/huge_memory: cleanup __split_unmapped_folio()
Date: Tue, 21 Oct 2025 21:21:38 +0000	[thread overview]
Message-ID: <20251021212142.25766-1-richard.weiyang@gmail.com> (raw)

This short patch series cleans up and optimizes the internal logic of
the __split_unmapped_folio() function.

The goal is to improve clarity and efficiency by eliminating redundant
checks, caching stable attribute values, and simplifying the iteration
logic used for updating folio statistics.

These changes make the code easier to follow and maintain.

The split_huge_page_test selftest pass.

v3:
  * only merge 4&5 in v1
  * refine the comment

v2:
  * merge patch 2-5
  * http://lkml.kernel.org/r/20251016004613.514-1-richard.weiyang@gmail.com

v1:
  * http://lkml.kernel.org/r/20251014134606.22543-1-richard.weiyang@gmail.com

Wei Yang (4):
  mm/huge_memory: avoid reinvoking folio_test_anon()
  mm/huge_memory: update folio stat after successful split
  mm/huge_memory: optimize and simplify folio stat update after split
  mm/huge_memory: optimize old_order derivation during folio splitting

 mm/huge_memory.c | 70 +++++++++++++++---------------------------------
 1 file changed, 21 insertions(+), 49 deletions(-)

-- 
2.34.1



             reply	other threads:[~2025-10-21 21:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 21:21 Wei Yang [this message]
2025-10-21 21:21 ` [Patch v3 1/4] mm/huge_memory: avoid reinvoking folio_test_anon() Wei Yang
2025-10-24 14:08   ` Lorenzo Stoakes
2025-10-21 21:21 ` [Patch v3 2/4] mm/huge_memory: update folio stat after successful split Wei Yang
2025-10-22 20:26   ` David Hildenbrand
2025-10-22 20:31   ` Zi Yan
2025-10-23  1:26   ` wang lian
2025-10-24 14:32   ` Lorenzo Stoakes
2025-10-31  0:46     ` Wei Yang
2025-10-21 21:21 ` [Patch v3 3/4] mm/huge_memory: optimize and simplify folio stat update after split Wei Yang
2025-10-22 20:28   ` David Hildenbrand
2025-10-22 20:32   ` Zi Yan
2025-10-23  1:29   ` wang lian
2025-10-24 14:35   ` Lorenzo Stoakes
2025-10-21 21:21 ` [Patch v3 4/4] mm/huge_memory: optimize old_order derivation during folio splitting Wei Yang
2025-10-22 20:29   ` David Hildenbrand
2025-10-22 20:33   ` Zi Yan
2025-10-23  1:32   ` wang lian
2025-10-24 14:46   ` Lorenzo Stoakes
2025-10-24 15:29     ` Zi Yan
2025-10-24 15:33       ` Lorenzo Stoakes
2025-10-31  1:50       ` Wei Yang
2025-10-31  1:55         ` Zi Yan
2025-10-31  2:00           ` Wei Yang

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=20251021212142.25766-1-richard.weiyang@gmail.com \
    --to=richard.weiyang@gmail.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=ryan.roberts@arm.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;
as well as URLs for NNTP newsgroup(s).