From: Qiang Gao <gaoqiangscut@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
linux-mm@kvack.org, bsingharora@gmail.com
Subject: Re: process hangs on do_exit when oom happens
Date: Tue, 23 Oct 2012 17:08:40 +0800 [thread overview]
Message-ID: <CAKWKT+ZG-Rw5spLUdn74H3QQ1RGrax2B4X_ksZB-OCHY5WXC6w@mail.gmail.com> (raw)
In-Reply-To: <20121023083556.GB15397@dhcp22.suse.cz>
this is just an example to show how to reproduce. actually,the first time I saw
this situation was on a machine with 288G RAM with many tasks running and
we limit 30G for each. but finanlly, no one exceeds this limit the the system
oom.
On Tue, Oct 23, 2012 at 4:35 PM, Michal Hocko <mhocko@suse.cz> wrote:
> On Tue 23-10-12 11:35:52, Qiang Gao wrote:
>> I'm sure this is a global-oom,not cgroup-oom. [the dmesg output in the end]
>
> Yes this is the global oom killer because:
>> cglimit -M 700M ./tt
>> then after global-oom,the process hangs..
>
>> 179184 pages RAM
>
> So you have ~700M of RAM so the memcg limit is basically pointless as it
> cannot be reached...
> --
> Michal Hocko
> SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-10-23 9:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.wmbi5kbrn27o5l@gaoqiang-d1.corp.qihoo.net>
2012-10-19 16:04 ` Michal Hocko
2012-10-22 2:16 ` Qiang Gao
2012-10-22 5:38 ` Balbir Singh
2012-10-22 13:01 ` Michal Hocko
2012-10-22 4:26 ` Qiang Gao
2012-10-23 3:35 ` Qiang Gao
2012-10-23 4:40 ` Balbir Singh
2012-10-23 7:18 ` Qiang Gao
2012-10-23 9:50 ` Michal Hocko
2012-10-23 10:10 ` Qiang Gao
2012-10-23 10:15 ` Michal Hocko
2012-10-23 17:43 ` Balbir Singh
2012-10-24 3:44 ` Qiang Gao
2012-10-25 9:57 ` Michal Hocko
2012-10-26 2:42 ` Qiang Gao
2012-10-26 17:03 ` Mike Galbraith
2012-10-26 20:04 ` Mike Galbraith
2012-10-23 8:35 ` Michal Hocko
2012-10-23 9:08 ` Qiang Gao [this message]
2012-10-23 9:43 ` Michal Hocko
2012-10-23 9:01 ` Sha Zhengju
2012-10-23 9:10 ` Qiang Gao
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=CAKWKT+ZG-Rw5spLUdn74H3QQ1RGrax2B4X_ksZB-OCHY5WXC6w@mail.gmail.com \
--to=gaoqiangscut@gmail.com \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mhocko@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