From: Gavin Guo <gavinguo@igalia.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org
Cc: gshan@redhat.com, david@redhat.com, willy@infradead.org,
ziy@nvidia.com, linmiaohe@huawei.com, hughd@google.com,
revest@google.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Clean up split_huge_pmd_locked() and remove unnecessary folio pointers
Date: Fri, 25 Apr 2025 18:38:57 +0800 [thread overview]
Message-ID: <20250425103859.825879-1-gavinguo@igalia.com> (raw)
The patch series enhance the folio verification by leveraging the
existing page_vma_mapped_walk() mechanism and removing redundant
folio pointers passing.
Link: https://lore.kernel.org/all/98d1d195-7821-4627-b518-83103ade56c0@redhat.com/
Link: https://lore.kernel.org/all/91599a3c-e69e-4d79-bac5-5013c96203d7@redhat.com/
Gavin Guo (2):
mm/huge_memory: Adjust try_to_migrate_one() and
split_huge_pmd_locked()
mm/huge_memory: Remove useless folio pointers passing
include/linux/huge_mm.h | 15 +++++++--------
mm/huge_memory.c | 37 ++++++++++---------------------------
mm/memory.c | 4 ++--
mm/mprotect.c | 2 +-
mm/rmap.c | 20 ++++++++++----------
5 files changed, 30 insertions(+), 48 deletions(-)
V1 -> V2:
1). Separate the logic into
- Adjust try_to_migrate_one() and split_huge_pmd_locked
- Remove useless folio pointers passing
2). Remove the unnecessary comments and brances around if condition.
base-commit: 02ddfb981de88a2c15621115dd7be2431252c568
prerequisite-patch-id: 9c9c975b11ad0f73acd863049b4f1732caa04e53
--
2.43.0
next reply other threads:[~2025-04-25 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:38 Gavin Guo [this message]
2025-04-25 10:38 ` [PATCH v2 1/2] mm/huge_memory: Adjust try_to_migrate_one() and split_huge_pmd_locked() Gavin Guo
2025-04-25 11:10 ` Zi Yan
2025-04-25 11:23 ` David Hildenbrand
2025-04-25 11:39 ` Zi Yan
2025-04-27 6:05 ` Baolin Wang
2025-04-25 10:38 ` [PATCH v2 2/2] mm/huge_memory: Remove useless folio pointers passing Gavin Guo
2025-04-25 11:40 ` Zi Yan
2025-04-27 6:06 ` Baolin Wang
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=20250425103859.825879-1-gavinguo@igalia.com \
--to=gavinguo@igalia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gshan@redhat.com \
--cc=hughd@google.com \
--cc=kernel-dev@igalia.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=revest@google.com \
--cc=willy@infradead.org \
--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