From: Vlastimil Babka <vbabka@suse.cz>
To: Zi Yan <ziy@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Cc: Rik van Riel <riel@surriel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/compaction: count pages and stop correctly during page isolation.
Date: Fri, 30 Oct 2020 15:50:04 +0100 [thread overview]
Message-ID: <16bdfad8-05f9-6ecf-0db6-c2dcf8e60309@suse.cz> (raw)
In-Reply-To: <20201029200435.3386066-1-zi.yan@sent.com>
On 10/29/20 9:04 PM, Zi Yan wrote:
> From: Zi Yan <ziy@nvidia.com>
>
> In isolate_migratepages_block, when cc->alloc_contig is true, we are
> able to isolate compound pages, nr_migratepages and nr_isolated did not
> count compound pages correctly, causing us to isolate more pages than we
> thought. Use thp_nr_pages to count pages. Otherwise, we might be trapped
> in too_many_isolated while loop, since the actual isolated pages can go
> up to COMPACT_CLUSTER_MAX*512=16384, where COMPACT_CLUSTER_MAX is 32,
> since we stop isolation after cc->nr_migratepages reaches to
> COMPACT_CLUSTER_MAX.
I wonder if a better fix would be to adjust the too_many_isolated() check so
that if we have non-zero cc->nr_migratepages, we bail out from further isolation
and migrate what we have immediately, instead of looping.
Because I can also imagine a hypothetical situation where multiple threads in
parallel cause too_many_isolated() to be true, and will all loop there forever.
The proposed fix should prevent such situation as well, AFAICT.
> In addition, after we fix the issue above, cc->nr_migratepages could
> never be equal to COMPACT_CLUSTER_MAX if compound pages are isolated,
> thus page isolation could not stop as we intended. Change the isolation
> stop condition to >=.
>
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> ---
> mm/compaction.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/mm/compaction.c b/mm/compaction.c
> index ee1f8439369e..0683a4999581 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1012,8 +1012,8 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
>
> isolate_success:
> list_add(&page->lru, &cc->migratepages);
> - cc->nr_migratepages++;
> - nr_isolated++;
> + cc->nr_migratepages += thp_nr_pages(page);
> + nr_isolated += thp_nr_pages(page);
>
> /*
> * Avoid isolating too much unless this block is being
> @@ -1021,7 +1021,7 @@ isolate_migratepages_block(struct compact_control *cc, unsigned long low_pfn,
> * or a lock is contended. For contention, isolate quickly to
> * potentially remove one source of contention.
> */
> - if (cc->nr_migratepages == COMPACT_CLUSTER_MAX &&
> + if (cc->nr_migratepages >= COMPACT_CLUSTER_MAX &&
> !cc->rescan && !cc->contended) {
> ++low_pfn;
> break;
> @@ -1132,7 +1132,7 @@ isolate_migratepages_range(struct compact_control *cc, unsigned long start_pfn,
> if (!pfn)
> break;
>
> - if (cc->nr_migratepages == COMPACT_CLUSTER_MAX)
> + if (cc->nr_migratepages >= COMPACT_CLUSTER_MAX)
> break;
> }
>
>
next prev parent reply other threads:[~2020-10-30 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 20:04 Zi Yan
2020-10-29 21:14 ` Yang Shi
2020-10-29 21:31 ` Zi Yan
2020-10-30 0:28 ` Andrew Morton
2020-10-30 1:20 ` Zi Yan
2020-10-30 9:43 ` Michal Hocko
2020-10-30 12:20 ` Zi Yan
2020-10-30 13:36 ` Michal Hocko
2020-10-30 14:35 ` Zi Yan
2020-10-30 14:49 ` Michal Hocko
2020-10-30 14:53 ` Zi Yan
2020-10-30 14:55 ` Vlastimil Babka
2020-10-30 18:33 ` Yang Shi
2020-10-30 18:39 ` Zi Yan
2020-10-30 18:55 ` Yang Shi
2020-11-02 13:03 ` Vlastimil Babka
2020-11-02 16:39 ` Yang Shi
2020-10-30 14:50 ` Vlastimil Babka [this message]
2020-10-30 15:18 ` Zi Yan
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=16bdfad8-05f9-6ecf-0db6-c2dcf8e60309@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.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
all inboxes | Powered by JetHome®