From: Michal Hocko <mhocko@kernel.org>
To: zhong jiang <zhongjiang@huawei.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Hugh Dickins <hughd@google.com>, Minchan Kim <minchan@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Linux Memory Management List <linux-mm@kvack.org>,
"Wangkefeng (Kevin)" <wangkefeng.wang@huawei.com>
Subject: Re: Frequent oom introduced in mainline when migrate_highatomic replace migrate_reserve
Date: Mon, 24 Jun 2019 10:10:11 +0200 [thread overview]
Message-ID: <20190624081011.GA11400@dhcp22.suse.cz> (raw)
In-Reply-To: <5D1054EE.20402@huawei.com>
On Mon 24-06-19 12:43:26, zhong jiang wrote:
> Recently, I hit an frequent oom issue in linux-4.4 stable with less than 4M free memory after
> the machine boots up.
Is this is a regression? Could you share the oom report?
> As the process is created, kernel stack will use the higher order to allocate continuous memory.
> Due to the fragmentabtion, we fails to allocate the memory. And the low memory will result
> in hardly memory compction. hence, it will easily to reproduce the oom.
How get your get such a large fragmentation that you cannot allocate
order-1 pages and compaction is not making any progress?
> But if we use migrate_reserve to reserve at least a pageblock at the boot stage. we can use
> the reserve memory to allocate continuous memory for process when the system is under
> severerly fragmentation.
Well, any reservation is a finite resource so I am not sure how that can
help universally. But your description is quite vague. Could you be more
specific about that workload? Also do you see the same with the current
upstream kernel as well?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-06-24 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 4:43 Frequent oom introduced in mainline when migrate_highatomic replace migrate_reserve zhong jiang
2019-06-24 8:10 ` Michal Hocko [this message]
2019-06-24 13:11 ` zhong jiang
2019-06-24 14:01 ` Michal Hocko
2019-06-24 15:28 ` zhong jiang
2019-06-24 16:47 ` zhong jiang
2019-06-24 17:54 ` Michal Hocko
2019-06-25 2:52 ` zhong jiang
2019-06-25 10:36 ` Michal Hocko
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=20190624081011.GA11400@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=zhongjiang@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).