From: Zi Yan <ziy@nvidia.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: akpm@linux-foundation.org, shy828301@gmail.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: migrate: Correct the hugetlb migration stats
Date: Fri, 29 Oct 2021 11:43:51 -0400 [thread overview]
Message-ID: <677EF981-F33E-4002-AA38-DD669C319284@nvidia.com> (raw)
In-Reply-To: <b35e54802a9a82d03d24845b463e9d9a68f7fd6b.1635491660.git.baolin.wang@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 2657 bytes --]
On 29 Oct 2021, at 3:42, Baolin Wang wrote:
> Now hugetlb migration is also available for some scenarios, such as
> soft offling or memory compaction. So we should correct the migration
hugetlb migration is available at the time if (PageHuge(page)) branch
is added. I am not sure what is new here.
> stats for hugetlb with using compound_nr() instead of thp_nr_pages()
> to get the number of pages.
nr_failed records the number of pages, not subpages. It is returned to
user space when move_pages() syscall is used. After your change,
if users try to migrate a list of pages including THPs and/or hugetlb
pages and some of THPs and/or hugetlb fail to migrate, move_pages()
will return a number larger than the number of pages the users tried
to migrate. I am not sure this is the change we want. Or at least,
the comment of migrate_pages() and the manpage of move_pages() need
to be changed and linux-api mailing list should be cc’d.
>
> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> ---
> mm/migrate.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/mm/migrate.c b/mm/migrate.c
> index a11e948..2b45a29 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -1475,7 +1475,7 @@ int migrate_pages(struct list_head *from, new_page_t get_new_page,
> * during migration.
> */
> is_thp = PageTransHuge(page) && !PageHuge(page);
> - nr_subpages = thp_nr_pages(page);
> + nr_subpages = compound_nr(page);
> cond_resched();
>
> if (PageHuge(page))
> @@ -1540,7 +1540,7 @@ int migrate_pages(struct list_head *from, new_page_t get_new_page,
> nr_failed += nr_subpages;
> goto out;
> }
> - nr_failed++;
> + nr_failed += nr_subpages;
> goto out;
> case -EAGAIN:
> if (is_thp) {
> @@ -1550,14 +1550,14 @@ int migrate_pages(struct list_head *from, new_page_t get_new_page,
> retry++;
> break;
> case MIGRATEPAGE_SUCCESS:
> + nr_succeeded += nr_subpages;
> if (is_thp) {
> nr_thp_succeeded++;
> - nr_succeeded += nr_subpages;
> break;
> }
> - nr_succeeded++;
> break;
> default:
> + nr_failed += nr_subpages;
> /*
> * Permanent failure (-EBUSY, etc.):
> * unlike -EAGAIN case, the failed page is
> @@ -1566,10 +1566,8 @@ int migrate_pages(struct list_head *from, new_page_t get_new_page,
> */
> if (is_thp) {
> nr_thp_failed++;
> - nr_failed += nr_subpages;
> break;
> }
> - nr_failed++;
> break;
> }
> }
> --
> 1.8.3.1
--
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2021-10-29 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 7:42 Baolin Wang
2021-10-29 15:43 ` Zi Yan [this message]
2021-11-01 6:54 ` Baolin Wang
2021-11-01 15:12 ` Zi Yan
2021-11-02 6:08 ` Baolin Wang
2021-11-02 19:30 ` Zi Yan
2021-11-03 8:07 ` Baolin Wang
2021-11-03 11:09 ` 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=677EF981-F33E-4002-AA38-DD669C319284@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.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