From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Huang Ying <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alistair Popple <apopple@nvidia.com>,
David Hildenbrand <david@redhat.com>,
Yang Shi <shy828301@gmail.com>, Zi Yan <ziy@nvidia.com>
Subject: Re: [PATCH] migrate_pages_batch: fix statistics for longterm pin retry
Date: Wed, 19 Apr 2023 15:34:54 +0800 [thread overview]
Message-ID: <e01cdedf-243d-038e-bb77-aea34e39658c@linux.alibaba.com> (raw)
In-Reply-To: <20230416235929.1040194-1-ying.huang@intel.com>
On 4/17/2023 7:59 AM, Huang Ying wrote:
> In commit fd4a7ac32918 ("mm: migrate: try again if THP split is failed
> due to page refcnt"), if the THP splitting fails due to page reference
> count, we will retry to improve migration successful rate. But the
> failed splitting is counted as migration failure and migration retry,
> which will cause duplicated failure counting. So, in this patch, this
> is fixed via undoing the failure counting if we decide to retry. The
> patch is tested via failure injection.
Makes sense to me. Thanks.
Reviewed-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> Fixes: fd4a7ac32918 ("mm: migrate: try again if THP split is failed due to page refcnt")
> Signed-off-by: "Huang, Ying" <ying.huang@intel.com>
> Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
> Cc: Alistair Popple <apopple@nvidia.com>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Yang Shi <shy828301@gmail.com>
> Cc: Zi Yan <ziy@nvidia.com>
> ---
> mm/migrate.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/mm/migrate.c b/mm/migrate.c
> index b34a0f383795..47a1e8445f45 100644
> --- a/mm/migrate.c
> +++ b/mm/migrate.c
> @@ -1743,6 +1743,9 @@ static int migrate_pages_batch(struct list_head *from, new_page_t get_new_page,
> large_retry++;
> thp_retry += is_thp;
> nr_retry_pages += nr_pages;
> + /* Undo duplicated failure counting. */
> + nr_large_failed--;
> + stats->nr_thp_failed -= is_thp;
> break;
> }
> }
prev parent reply other threads:[~2023-04-19 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 23:59 Huang Ying
2023-04-19 7:34 ` Baolin Wang [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=e01cdedf-243d-038e-bb77-aea34e39658c@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=ying.huang@intel.com \
--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