From: Satoru Moriya <satoru.moriya.br@hitachi.com>
To: kamezawa.hiroyu@jp.fujitsu.com
Cc: linux-mm@kvack.org, satoshi.oshima.fk@hitachi.com,
taketoshi.sakuraba.hc@hitachi.com
Subject: Re: Problem with oom-killer in memcg
Date: Wed, 27 May 2009 16:04:21 +0900 [thread overview]
Message-ID: <4A1CE5F5.7080207@hitachi.com> (raw)
In-Reply-To: <20090527101039.f9de2229.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> How many cpus are you using ?
I'm using Xeon E5345(4 core).
> I think Balbir (and other people) is planning to add "oom handler" for memcg
> or oom handler cgroup. But we need more study.
Thank you for sharing that with me.
> I assume that you use x86. If so, current bahavior is a bit complicated.
>
> do_page_fault()
> -> allocate and charge memory account
> -> memcg's oom kill is called
> -> no progress.
> User says "don't use OOM Kill" but no other way than "OOM Kill"
>
> We don't have much choices here..
> - kill in force ?
> - add some sleep ?
> - freeze cgroup under OOM ? (this seems not easy)
> - Ask admin to increase size of memory limit ?
>
> Thank you for reporting, but I can't think of quick fix right now.
> I'll remember this in my TO-DO List.
Ok, thank you very much.
--
---
Satoru MORIYA
Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: satoru.moriya.br@hitachi.com
--
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>
prev parent reply other threads:[~2009-05-27 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 10:04 Satoru Moriya
2009-05-27 1:10 ` KAMEZAWA Hiroyuki
2009-05-27 7:04 ` Satoru Moriya [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=4A1CE5F5.7080207@hitachi.com \
--to=satoru.moriya.br@hitachi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=satoshi.oshima.fk@hitachi.com \
--cc=taketoshi.sakuraba.hc@hitachi.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