From: Vlastimil Babka <vbabka@suse.cz>
To: Baolin Wang <baolin.wang@linux.alibaba.com>, akpm@linux-foundation.org
Cc: mgorman@techsingularity.net, osalvador@suse.de,
william.lam@bytedance.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mm: compaction: consider the number of scanning compound pages in isolate fail path
Date: Wed, 15 Mar 2023 16:54:31 +0100 [thread overview]
Message-ID: <258932e0-a2a6-7f17-014c-05676bfad456@suse.cz> (raw)
In-Reply-To: <1bc1c955b03603c4e14f56dfbbef9f637f18dbbd.1678703534.git.baolin.wang@linux.alibaba.com>
On 3/13/23 11:37, Baolin Wang wrote:
> The commit b717d6b93b54 ("mm: compaction: include compound page count
> for scanning in pageblock isolation") had added compound page statistics
> for scanning in pageblock isolation, to make sure the number of scanned
> pages are always larger than the number of isolated pages when isolating
> mirgratable or free pageblock.
>
> However, when failed to isolate the pages when scanning the mirgratable or
> free pageblock, the isolation failure path did not consider the scanning
> statistics of the compound pages, which can show the incorrect number of
> scanned pages in tracepoints or the vmstats to make people confusing about
> the page scanning pressure in memory compaction.
>
> Thus we should take into account the number of scanning pages when failed
> to isolate the compound pages to make the statistics accurate.
>
> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> ---
> mm/compaction.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index 5a9501e0ae01..c9d9ad958e2a 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -587,6 +587,7 @@ static unsigned long isolate_freepages_block(struct compact_control *cc,
> blockpfn += (1UL << order) - 1;
> cursor += (1UL << order) - 1;
> }
> + nr_scanned += (1UL << order) - 1;
I'd rather put it in the block above that tests order < MAX_ORDER. Otherwise
as the comments say, the value can be bogus as it's racy.
> goto isolate_fail;
> }
>
> @@ -873,9 +874,8 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
> cond_resched();
> }
>
> - nr_scanned++;
> -
> page = pfn_to_page(low_pfn);
> + nr_scanned += compound_nr(page);
For the same reason, I'd rather leave the nr_scanned adjustment by order in
the specific code blocks where we know/think we have a compound or huge page
and have sanity checked the order/nr_pages, and not add an unchecked
compound_nr() here.
Thanks.
>
> /*
> * Check if the pageblock has already been marked skipped.
> @@ -1077,6 +1077,7 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
> */
> if (unlikely(PageCompound(page) && !cc->alloc_contig)) {
> low_pfn += compound_nr(page) - 1;
> + nr_scanned += compound_nr(page) - 1;
> SetPageLRU(page);
> goto isolate_fail_put;
> }
> @@ -1097,7 +1098,6 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
> isolate_success_no_list:
> cc->nr_migratepages += compound_nr(page);
> nr_isolated += compound_nr(page);
> - nr_scanned += compound_nr(page) - 1;
>
> /*
> * Avoid isolating too much unless this block is being
next prev parent reply other threads:[~2023-03-15 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 10:37 Baolin Wang
2023-03-13 10:37 ` [PATCH 2/2] mm: compaction: fix the possible deadlock when isolating hugetlb pages Baolin Wang
2023-03-13 17:08 ` Mike Kravetz
2023-03-13 19:31 ` Andrew Morton
2023-03-14 4:11 ` Baolin Wang
2023-03-14 17:27 ` Mike Kravetz
2023-03-15 1:27 ` Baolin Wang
2023-03-15 17:17 ` Vlastimil Babka
2023-03-15 15:54 ` Vlastimil Babka [this message]
2023-03-16 9:53 ` [PATCH 1/2] mm: compaction: consider the number of scanning compound pages in isolate fail path 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=258932e0-a2a6-7f17-014c-05676bfad456@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=william.lam@bytedance.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