From: Zi Yan <ziy@nvidia.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v1 1/2] mm/migrate: make migrate_misplaced_folio() return 0 on success
Date: Thu, 20 Jun 2024 21:40:56 -0400 [thread overview]
Message-ID: <6C1F89D6-7093-4225-A1D1-E64655BD8A4C@nvidia.com> (raw)
In-Reply-To: <20240620212935.656243-2-david@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On 20 Jun 2024, at 17:29, David Hildenbrand wrote:
> Let's just return 0 on success, which is less confusing.
>
> ... especially because we got it wrong in the migrate.h stub where we
> have "return -EAGAIN; /* can't migrate now */" instead of "return 0;".
> Likely this wrong return value doesn't currently matter, but it
> certainly adds confusion.
>
> We'll add migrate_misplaced_folio_prepare() next, where we want to use
> the same "return 0 on success" approach, so let's just clean this up.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> mm/huge_memory.c | 5 ++---
> mm/memory.c | 2 +-
> mm/migrate.c | 4 ++--
> 3 files changed, 5 insertions(+), 6 deletions(-)
>
LGTM. Reviewed-by: Zi Yan <ziy@nvidia.com>
--
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2024-06-21 1:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 21:29 [PATCH v1 0/2] mm/migrate: move NUMA hinting fault folio isolation + checks under PTL David Hildenbrand
2024-06-20 21:29 ` [PATCH v1 1/2] mm/migrate: make migrate_misplaced_folio() return 0 on success David Hildenbrand
2024-06-21 1:40 ` Zi Yan [this message]
2024-06-21 3:39 ` Baolin Wang
2024-07-01 7:36 ` Huang, Ying
2024-07-01 7:44 ` David Hildenbrand
2024-06-20 21:29 ` [PATCH v1 2/2] mm/migrate: move NUMA hinting fault folio isolation + checks under PTL David Hildenbrand
2024-06-21 2:05 ` Zi Yan
2024-06-21 7:32 ` David Hildenbrand
2024-06-21 4:07 ` Baolin Wang
2024-06-21 7:31 ` David Hildenbrand
2024-06-21 13:44 ` Zi Yan
2024-06-21 20:18 ` David Hildenbrand
2024-06-21 20:48 ` Zi Yan
2024-06-26 16:49 ` David Hildenbrand
2024-06-26 17:37 ` Zi Yan
2024-07-01 8:32 ` Huang, Ying
2024-07-01 13:50 ` Zi Yan
2024-07-01 14:03 ` David Hildenbrand
2024-07-01 14:04 ` Zi Yan
2024-06-21 17:47 ` Donet Tom
2024-06-21 20:14 ` David Hildenbrand
2024-06-26 16:22 ` David Hildenbrand
2024-06-27 6:00 ` Donet Tom
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=6C1F89D6-7093-4225-A1D1-E64655BD8A4C@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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