From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Tejun Heo <tj@kernel.org>,
Mel Gorman <mgorman@suse.de>, Oleg Nesterov <oleg@redhat.com>,
Rik van Riel <riel@redhat.com>, Jianguo Wu <wujianguo@huawei.com>,
Tim Hockin <thockin@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [patch 11/11] mm, memcg: allow system oom killer to be disabled
Date: Tue, 4 Mar 2014 19:59:46 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1403041957340.8067@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403041952170.8067@chino.kir.corp.google.com>
Now that system oom conditions can properly be handled from userspace,
allow the oom killer to be disabled. Otherwise, the kernel will
immediately kill a process and memory will be freed. The userspace oom
handler may have a different policy.
Signed-off-by: David Rientjes <rientjes@google.com>
---
Documentation/cgroups/memory.txt | 4 ++--
include/linux/memcontrol.h | 6 ++++++
mm/memcontrol.c | 11 ++++++++---
mm/oom_kill.c | 3 +++
4 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -755,8 +755,8 @@ You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
# echo 1 > memory.oom_control
-This operation is only allowed to the top cgroup of a sub-hierarchy and does
-not include the root memcg.
+This operation is only allowed to the top cgroup of a sub-hierarchy. If
+disabled for the root memcg, the system oom killer is disabled.
If OOM-killer is disabled, tasks under cgroup will hang/sleep
in memory cgroup's OOM-waitqueue when they request accountable memory.
diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
--- a/include/linux/memcontrol.h
+++ b/include/linux/memcontrol.h
@@ -159,6 +159,7 @@ bool mem_cgroup_oom_synchronize(bool wait);
extern bool mem_cgroup_alloc_use_oom_reserve(void);
extern u64 mem_cgroup_root_oom_reserve(void);
extern void mem_cgroup_root_oom_notify(void);
+extern bool mem_cgroup_root_oom_disable(void);
#ifdef CONFIG_MEMCG_SWAP
extern int do_swap_account;
@@ -415,6 +416,11 @@ static inline void mem_cgroup_root_oom_notify(void)
{
}
+static inline bool mem_cgroup_root_oom_disable(void)
+{
+ return false;
+}
+
static inline void mem_cgroup_inc_page_stat(struct page *page,
enum mem_cgroup_stat_index idx)
{
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -5976,13 +5976,13 @@ static int mem_cgroup_oom_control_write(struct cgroup_subsys_state *css,
struct mem_cgroup *memcg = mem_cgroup_from_css(css);
struct mem_cgroup *parent = mem_cgroup_from_css(css_parent(&memcg->css));
- /* cannot set to root cgroup and only 0 and 1 are allowed */
- if (!parent || !((val == 0) || (val == 1)))
+ /* only 0 and 1 are allowed */
+ if (val != !!val)
return -EINVAL;
mutex_lock(&memcg_create_mutex);
/* oom-kill-disable is a flag for subhierarchy. */
- if ((parent->use_hierarchy) || memcg_has_children(memcg)) {
+ if (parent && (parent->use_hierarchy || memcg_has_children(memcg))) {
mutex_unlock(&memcg_create_mutex);
return -EINVAL;
}
@@ -6062,6 +6062,11 @@ u64 mem_cgroup_root_oom_reserve(void)
return root_mem_cgroup->oom_reserve >> PAGE_SHIFT;
}
+bool mem_cgroup_root_oom_disable(void)
+{
+ return root_mem_cgroup->oom_kill_disable;
+}
+
#ifdef CONFIG_MEMCG_KMEM
static int memcg_init_kmem(struct mem_cgroup *memcg, struct cgroup_subsys *ss)
{
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -656,6 +656,9 @@ void out_of_memory(struct zonelist *zonelist, gfp_t gfp_mask,
mpol_mask = (constraint == CONSTRAINT_MEMORY_POLICY) ? nodemask : NULL;
check_panic_on_oom(constraint, gfp_mask, order, mpol_mask);
+ if (mem_cgroup_root_oom_disable())
+ return;
+
if (sysctl_oom_kill_allocating_task && current->mm &&
!oom_unkillable_task(current, NULL, nodemask) &&
current->signal->oom_score_adj != OOM_SCORE_ADJ_MIN) {
--
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:[~2014-03-05 3:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 3:58 [patch 00/11] userspace out of memory handling David Rientjes
2014-03-05 3:58 ` [patch 01/11] fork: collapse copy_flags into copy_process David Rientjes
2014-03-05 3:58 ` [patch 02/11] mm, mempolicy: rename slab_node for clarity David Rientjes
2014-03-05 3:59 ` [patch 03/11] mm, mempolicy: remove per-process flag David Rientjes
2014-03-07 17:20 ` Andi Kleen
2014-03-07 20:48 ` Andrew Morton
2014-03-05 3:59 ` [patch 04/11] mm, memcg: add tunable for oom reserves David Rientjes
2014-03-05 21:17 ` Andrew Morton
2014-03-06 2:53 ` David Rientjes
2014-03-06 21:04 ` Tejun Heo
2014-03-05 3:59 ` [patch 05/11] res_counter: remove interface for locked charging and uncharging David Rientjes
2014-03-05 3:59 ` [patch 06/11] res_counter: add interface for maximum nofail charge David Rientjes
2014-03-05 3:59 ` [patch 07/11] mm, memcg: allow processes handling oom notifications to access reserves David Rientjes
2014-03-06 21:12 ` Tejun Heo
2014-03-05 3:59 ` [patch 08/11] mm, memcg: add memcg oom reserve documentation David Rientjes
2014-03-05 3:59 ` [patch 09/11] mm, page_alloc: allow system oom handlers to use memory reserves David Rientjes
2014-03-06 21:13 ` Tejun Heo
2014-03-05 3:59 ` [patch 10/11] mm, memcg: add memory.oom_control notification for system oom David Rientjes
2014-03-06 21:15 ` Tejun Heo
2014-03-05 3:59 ` David Rientjes [this message]
2014-03-06 21:15 ` [patch 11/11] mm, memcg: allow system oom killer to be disabled Tejun Heo
2014-03-05 21:17 ` [patch 00/11] userspace out of memory handling Andrew Morton
2014-03-06 2:52 ` David Rientjes
2014-03-11 12:03 ` Jianguo Wu
2014-03-06 20:49 ` Tejun Heo
2014-03-06 20:55 ` David Rientjes
2014-03-06 20:59 ` Tejun Heo
2014-03-06 21:08 ` David Rientjes
2014-03-06 21:11 ` Tejun Heo
2014-03-06 21:23 ` David Rientjes
2014-03-06 21:29 ` Tejun Heo
2014-03-06 21:33 ` Tejun Heo
2014-03-07 12:23 ` 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=alpine.DEB.2.02.1403041957340.8067@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=cl@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=oleg@redhat.com \
--cc=penberg@kernel.org \
--cc=riel@redhat.com \
--cc=thockin@google.com \
--cc=tj@kernel.org \
--cc=wujianguo@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