From: Mike Kravetz <mike.kravetz@oracle.com>
To: Vlastimil Babka <vbabka@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: 'Joonsoo Kim' <iamjoonsoo.kim@lge.com>,
Laura Abbott <labbott@redhat.com>
Subject: Re: freepage accounting bug with CMA/migrate isolation
Date: Thu, 26 Jul 2018 09:50:32 -0700 [thread overview]
Message-ID: <fb90a412-ead7-0ada-c443-2bd1c41f2614@oracle.com> (raw)
In-Reply-To: <efc17c04-8498-29c8-56bb-9cbad897f0d8@suse.cz>
On 07/26/2018 05:28 AM, Vlastimil Babka wrote:
> On 07/24/2018 06:24 AM, 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.
>
> That means you count isolated pages as freepages, right?
Yes, I know it is not correct. But, just wanted to eliminate the
isolated pageblock special case for experimentation.
>> 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.
>
> Interesting, that should only matter in __free_one_page(). Do you have
> page guards enabled?
Nope, no page guards.
Do note that in this case, I added back all the special 'is_migrate_isolate'
checks. So, just stock 4.17 with the change to make pageblock_order equal
MAX_ORDER-1.
>> Just looking for suggesting in where/how to debug. I've been hacking on
>> this without much success.
As mentioned in my reply to Laura, I noticed that move_freepages_block()
can move more than a pageblock of pages. This is the case where page_order
of the (first) free page is > pageblock_order. Should only happen in the
set_migratetype_isolate case as unset has that check you added. This
generally 'works' as alloc_contig_range rounds up to MAX_ORDER(-1). So,
set and unset migrate isolate tend to balance out. But, I am wondering
if there might be some kind of race where someone could mess with those
pageblocks (and freepage counts) while we drop the zone lock. Trying to
put together a quick hack to test this theory, but it is more complicated
that first thought. :)
--
Mike Kravetz
next prev parent reply other threads:[~2018-07-26 16:50 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
2018-07-26 12:28 ` Vlastimil Babka
2018-07-26 16:50 ` Mike Kravetz [this message]
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=fb90a412-ead7-0ada-c443-2bd1c41f2614@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