From: Mike Kravetz <mike.kravetz@oracle.com>
To: Laura Abbott <labbott@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Vlastimil Babka <vbabka@suse.cz>, 'Joonsoo Kim' <iamjoonsoo.kim@lge.com>
Subject: Re: freepage accounting bug with CMA/migrate isolation
Date: Tue, 24 Jul 2018 17:46:11 -0700 [thread overview]
Message-ID: <1384e612-e664-6278-af22-9113c12f76d8@oracle.com> (raw)
In-Reply-To: <92636e32-c71b-0092-02bf-a802065075ef@redhat.com>
On 07/24/2018 03:38 PM, Laura Abbott wrote:
> On 07/23/2018 09:24 PM, Mike Kravetz wrote:
>> With v4.17, I can see an issue like those addressed in commits 3c605096d315
>> ("mm/page_alloc: restrict max order of merging on isolated pageblock")
>> and d9dddbf55667 ("mm/page_alloc: prevent merging between isolated and
>> other pageblocks"). After running a CMA stress test for a while, I see:
>> MemTotal: 8168384 kB
>> MemFree: 8457232 kB
>> MemAvailable: 9204844 kB
>> If I let the test run, MemFree and MemAvailable will continue to grow.
>>
>> I am certain the issue is with pageblocks of migratetype ISOLATED. If
>> I disable all special 'is_migrate_isolate' checks in freepage accounting,
>> the issue goes away. Further, I am pretty sure the issue has to do with
>> pageblock merging and or page orders spanning pageblocks. If I make
>> pageblock_order equal MAX_ORDER-1, the issue also goes away.
>>
>> Just looking for suggesting in where/how to debug. I've been hacking on
>> this without much success.
>> --
>> Mike Kravetz
>>
>
> If you revert d883c6cf3b39 ("Revert "mm/cma: manage the memory of the CMA
> area by using the ZONE_MOVABLE"") do you still see the issue? I thought
> there was another isolation edge case which was fixed by that series.
>
Thanks Laura,
Reverting that patch certainly seems to help. Although, I'm guessing there
is still some accounting issue even with the patch reverted.
Right after boot,
MemTotal: 8168380 kB
MemFree: 7233360 kB
MemAvailable: 7317704 kB
After stress testing for a couple hours,
MemTotal: 8168380 kB
MemFree: 7848468 kB
MemAvailable: 7634856 kB
While looking at the code, I did not like the way set_migratetype_isolate
may 'isolate' more than pageblock_nr_pages if there is a > pageblock_order
sized free page. This seems to work because alloc_contig_range always
aligns to MAX_ORDER-1. But, I'd like to change this and see if it helps.
--
Mike Kravetz
next prev parent reply other threads:[~2018-07-25 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 4:24 Mike Kravetz
2018-07-24 22:38 ` Laura Abbott
2018-07-25 0:46 ` Mike Kravetz [this message]
2018-07-26 12:28 ` Vlastimil Babka
2018-07-26 16:50 ` Mike Kravetz
2018-07-26 21:26 ` Vlastimil Babka
2018-07-26 13:30 ` Vlastimil Babka
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=1384e612-e664-6278-af22-9113c12f76d8@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=labbott@redhat.com \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
/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