From: Zi Yan <ziy@nvidia.com>
To: Gavin Guo <gavinguo@igalia.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, gshan@redhat.com,
david@redhat.com, willy@infradead.org, linmiaohe@huawei.com,
hughd@google.com, revest@google.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mm/huge_memory: Remove useless folio pointers passing
Date: Fri, 25 Apr 2025 07:40:11 -0400 [thread overview]
Message-ID: <618D4D49-EAE3-42EC-9B51-BB45996B7D2D@nvidia.com> (raw)
In-Reply-To: <20250425103859.825879-3-gavinguo@igalia.com>
On 25 Apr 2025, at 6:38, Gavin Guo wrote:
> Since the previous commit "mm/huge_memory: Adjust try_to_migrate_one() and
> split_huge_pmd_locked()" has simplified the logic by leveraging the
> folio verification in page_vma_mapped_walk(), this patch removes the
> unnecessary folio pointers passing.
>
> Suggested-by: David Hildenbrand <david@redhat.com>
> 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/
> Signed-off-by: Gavin Guo <gavinguo@igalia.com>
> Acked-by: David Hildenbrand <david@redhat.com>
> ---
> include/linux/huge_mm.h | 15 +++++++--------
> mm/huge_memory.c | 16 ++++++++--------
> mm/memory.c | 4 ++--
> mm/mprotect.c | 2 +-
> mm/rmap.c | 4 ++--
> 5 files changed, 20 insertions(+), 21 deletions(-)
>
LGTM. Thanks. Reviewed-by: Zi Yan <ziy@nvidia.com>
--
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-04-25 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:38 [PATCH v2 0/2] Clean up split_huge_pmd_locked() and remove unnecessary folio pointers Gavin Guo
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 [this message]
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=618D4D49-EAE3-42EC-9B51-BB45996B7D2D@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gavinguo@igalia.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 \
/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