From: David Rientjes <rientjes@google.com>
To: Xuzhichuang <xuzhichuang@huawei.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Songjiangtao (mygirlsjt)" <songjiangtao.song@huawei.com>,
"Zhangwei (FF)" <zw.zhang@huawei.com>,
Qiuxishi <qiuxishi@huawei.com>
Subject: Re: 答复: [BUG REPORT] OOM Killer is invoked while the system still has much memory
Date: Tue, 14 Jul 2015 18:57:14 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1507141855200.6993@chino.kir.corp.google.com> (raw)
In-Reply-To: <6D317A699782EA4DB9A0E6266C9219696CA2B45B@SZXEMA501-MBX.china.huawei.com>
On Wed, 15 Jul 2015, Xuzhichuang wrote:
> Hi,
>
> Thanks for your replying.
>
> According to the OOM message, OOM killer is invoked by the function seq_read, I found two patches in the latest kernel which can be avoid or fixed this problem.
>
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/fs/seq_file.c?id=058504edd02667eef8fac9be27ab3ea74332e9b4
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/fs/seq_file.c?id=5cec38ac866bfb8775638e71a86e4d8cac30caae
>
> As the patches said, it changed the seq_file code fallback to vmalloc allocations if kmalloc failed, instead of OOM kill processes.
>
Yes, we use those two patches as well internally. You may want to give
them a try if this is the only source of oom killer issues, but keep in
mind that other subsystems like the tcp layer will often do high-order
allocations as well. If you can free up some of that ZONE_DMA memory that
is unneeded with lowmem_reserve_ratio, you might get a little more room.
Good luck!
prev parent reply other threads:[~2015-07-15 1:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 7:11 [BUG REPORT] OOM Killer is invoked while the system still has much memory Xuzhichuang
2015-07-14 8:15 ` Michal Hocko
2015-07-14 8:42 ` Xishi Qiu
2015-07-14 9:00 ` Michal Hocko
2015-07-14 9:14 ` Xishi Qiu
2015-07-14 9:28 ` Michal Hocko
2015-07-14 9:50 ` Xishi Qiu
2015-07-15 0:09 ` David Rientjes
2015-07-15 1:46 ` 答复: " Xuzhichuang
2015-07-15 1:57 ` David Rientjes [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=alpine.DEB.2.10.1507141855200.6993@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@huawei.com \
--cc=songjiangtao.song@huawei.com \
--cc=xuzhichuang@huawei.com \
--cc=zw.zhang@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).