linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: Yang Shi <shy828301@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux MM <linux-mm@kvack.org>, Rik van Riel <riel@surriel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH] mm/compaction: count pages and stop correctly during page isolation.
Date: Thu, 29 Oct 2020 17:31:28 -0400	[thread overview]
Message-ID: <EC915762-AE2E-4ACB-AB27-E7C95A584A0C@nvidia.com> (raw)
In-Reply-To: <CAHbLzkpka7s1DFeXO5dxfGvxZFcTYb9KH0AE_AXuxeFO4q_rtg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3418 bytes --]

On 29 Oct 2020, at 17:14, Yang Shi wrote:

> On Thu, Oct 29, 2020 at 1:04 PM Zi Yan <zi.yan@sent.com> 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,
>
> Is it that easy to run into? 16384 doesn't seem like too many pages, just 64MB.

I hit this when I was running oom01 from ltp to test my PUD THP patchset, which
allocates PUD THPs from CMA regions and splits them into PMD THPs due to memory
pressure. I am not sure if it is common that in the upstream kernel PMD THPs will
be allocated in CMA regions due to allocation fallback.

>
>> since we stop isolation after cc->nr_migratepages reaches to
>> COMPACT_CLUSTER_MAX.
>>
>> 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 >=.
>
> The fix looks sane to me. Reviewed-by: Yang Shi <shy828301@gmail.com>

Thanks.

>
> Shall you add Fixes tag to commit
> 1da2f328fa643bd72197dfed0c655148af31e4eb? And may cc stable.

Sure.

Fixes: 1da2f328fa64 (“mm,thp,compaction,cma: allow THP migration for CMA allocations”)

stable cc’ed.

>
>>
>> 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;
>>         }
>>
>> --
>> 2.28.0
>>
>>


—
Best Regards,
Yan Zi

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

  reply	other threads:[~2020-10-29 21:31 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 [this message]
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
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=EC915762-AE2E-4ACB-AB27-E7C95A584A0C@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@surriel.com \
    --cc=shy828301@gmail.com \
    --cc=stable@vger.kernel.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