From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use oom_killer_disabled in all oom pathes
Date: Tue, 26 Apr 2011 11:57:13 +0900 (JST) [thread overview]
Message-ID: <20110426115902.F374.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20110426025429.GA11812@darkstar>
> oom_killer_disable should be a global switch, also fit for oom paths
> other than __alloc_pages_slowpath
>
> Here add it to mem_cgroup_handle_oom and pagefault_out_of_memory as well.
Can you please explain more? Why should? Now oom_killer_disabled is used
only hibernation path. so, Why pagefault and memcg allocation will be happen?
WARNING: multiple messages have this Message-ID (diff)
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use oom_killer_disabled in all oom pathes
Date: Tue, 26 Apr 2011 11:57:13 +0900 (JST) [thread overview]
Message-ID: <20110426115902.F374.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20110426025429.GA11812@darkstar>
> oom_killer_disable should be a global switch, also fit for oom paths
> other than __alloc_pages_slowpath
>
> Here add it to mem_cgroup_handle_oom and pagefault_out_of_memory as well.
Can you please explain more? Why should? Now oom_killer_disabled is used
only hibernation path. so, Why pagefault and memcg allocation will be happen?
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-26 2:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 2:54 [PATCH] use oom_killer_disabled in all oom pathes Dave Young
2011-04-26 2:54 ` Dave Young
2011-04-26 2:57 ` KOSAKI Motohiro [this message]
2011-04-26 2:57 ` KOSAKI Motohiro
2011-04-26 3:05 ` Dave Young
2011-04-26 3:05 ` Dave Young
2011-04-26 3:14 ` KOSAKI Motohiro
2011-04-26 3:14 ` KOSAKI Motohiro
2011-04-26 3:19 ` Dave Young
2011-04-26 3:19 ` Dave Young
2011-04-26 3:17 ` KAMEZAWA Hiroyuki
2011-04-26 3:17 ` KAMEZAWA Hiroyuki
2011-04-26 3:26 ` Dave Young
2011-04-26 3:26 ` Dave Young
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=20110426115902.F374.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.