From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Dan Williams <dan.j.williams@intel.com>,
Vlastimil Babka <vbabka@suse.cz>
Cc: Michal Hocko <mhocko@kernel.org>, Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next-20190214] Free pages statistics is broken.
Date: Sat, 16 Feb 2019 11:18:04 +0900 [thread overview]
Message-ID: <11e41efb-e04d-119c-fcaa-24a01b471930@i-love.sakura.ne.jp> (raw)
In-Reply-To: <CAPcyv4ihKWkONbnaParFKLke7sHBWJzXzN2auUKPQvhcEnJjdg@mail.gmail.com>
On 2019/02/16 3:13, Dan Williams wrote:
> On Fri, Feb 15, 2019 at 9:44 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>>
>> On 2/15/19 3:27 PM, Tetsuo Handa wrote:
>>> On 2019/02/15 22:01, Michal Hocko wrote:
>>>> On Fri 15-02-19 11:27:10, Tetsuo Handa wrote:
>>>>> I noticed that amount of free memory reported by DMA: / DMA32: / Normal: fields are
>>>>> increasing over time. Since 5.0-rc6 is working correctly, some change in linux-next
>>>>> is causing this problem.
>>>>
>>>> Just a shot into the dark. Could you try to disable the page allocator
>>>> randomization (page_alloc.shuffle kernel command line parameter)? Not
>>>> that I see any bug there but it is a recent change in the page allocator
>>>> I am aware of and it might have some anticipated side effects.
>>>>
>>>
>>> I tried CONFIG_SHUFFLE_PAGE_ALLOCATOR=n but problem still exists.
>>
>> I think it's the preparation patch [1], even with randomization off:
>>
>> @@ -1910,7 +1900,7 @@ static inline void expand(struct zone *zone, struct page *page,
>> if (set_page_guard(zone, &page[size], high, migratetype))
>> continue;
>>
>> - list_add(&page[size].lru, &area->free_list[migratetype]);
>> + add_to_free_area(&page[size], area, migratetype);
>> area->nr_free++;
>> set_page_order(&page[size], high);
>> }
>>
>> This should have removed the 'area->nr_free++;' line, as add_to_free_area()
>> includes the increment.
>
> Yes, good find! I'll send an incremental fixup patch in a moment
> unless someone beats me to it.
>
Removing the 'area->nr_free++;' line solved the problem. Thank you.
prev parent reply other threads:[~2019-02-16 2:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 2:27 Tetsuo Handa
2019-02-15 13:01 ` Michal Hocko
2019-02-15 14:27 ` Tetsuo Handa
2019-02-15 17:44 ` Vlastimil Babka
2019-02-15 18:13 ` Dan Williams
2019-02-16 2:18 ` Tetsuo Handa [this message]
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=11e41efb-e04d-119c-fcaa-24a01b471930@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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