From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next-20190214] Free pages statistics is broken.
Date: Fri, 15 Feb 2019 14:01:47 +0100 [thread overview]
Message-ID: <20190215130147.GZ4525@dhcp22.suse.cz> (raw)
In-Reply-To: <201902150227.x1F2RBhh041762@www262.sakura.ne.jp>
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.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-02-15 13:01 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 [this message]
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
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=20190215130147.GZ4525@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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