From: Zi Yan <ziy@nvidia.com>
To: Byungchul Park <byungchul@sk.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel_team@skhynix.com, akpm@linux-foundation.org,
shivankg@amd.com
Subject: Re: [PATCH v2] mm: separate move/undo parts from migrate_pages_batch()
Date: Wed, 15 Jan 2025 10:05:57 -0500 [thread overview]
Message-ID: <C401E7A1-9C5A-48F4-BEF4-9D9439A86AA9@nvidia.com> (raw)
In-Reply-To: <20250115103403.11882-1-byungchul@sk.com>
On 15 Jan 2025, at 5:34, Byungchul Park wrote:
> Changes from v1
> - Fix a wrong coding style
>
> --->8---
> From a65a6e4975962707bf87171e317f005c6276887e Mon Sep 17 00:00:00 2001
> From: Byungchul Park <byungchul@sk.com>
> Date: Thu, 8 Aug 2024 15:53:58 +0900
> Subject: [PATCH v2] mm: separate move/undo parts from migrate_pages_batch()
>
> Functionally, no change. This is a preparation for luf mechanism that
> requires to use separated folio lists for its own handling during
> migration. Refactored migrate_pages_batch() so as to separate move/undo
> parts from migrate_pages_batch().
>
> Signed-off-by: Byungchul Park <byungchul@sk.com>
> Reviewed-by: Shivank Garg <shivankg@amd.com>
> ---
> mm/migrate.c | 134 +++++++++++++++++++++++++++++++--------------------
> 1 file changed, 83 insertions(+), 51 deletions(-)
>
LGTM. Reviewed-by: Zi Yan <ziy@nvidia.com>
I am planning to send the batching page copy part in my page migration
acceleration patchset separately for upstream first, so that we can
focus on the page copy acceleration, using multithreads and DMA
afterwards.
Best Regards,
Yan, Zi
prev parent reply other threads:[~2025-01-15 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 9:53 [PATCH] " Byungchul Park
2025-01-15 10:07 ` Shivank Garg
2025-01-15 10:23 ` Byungchul Park
2025-01-15 10:34 ` [PATCH v2] " Byungchul Park
2025-01-15 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=C401E7A1-9C5A-48F4-BEF4-9D9439A86AA9@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=byungchul@sk.com \
--cc=kernel_team@skhynix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shivankg@amd.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