Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751404AbdFDTaP (ORCPT ); Sun, 4 Jun 2017 15:30:15 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:33483 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751169AbdFDTaI (ORCPT ); Sun, 4 Jun 2017 15:30:08 -0400 Date: Sun, 4 Jun 2017 22:30:02 +0300 From: Vladimir Davydov To: Roman Gushchin Cc: linux-mm@kvack.org, Tejun Heo , Johannes Weiner , Li Zefan , Michal Hocko , Tetsuo Handa , kernel-team@fb.com, cgroups@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v2 4/7] mm, oom: introduce oom_kill_all_tasks option for memory cgroups Message-ID: <20170604193002.GB19980@esperanza> References: <1496342115-3974-1-git-send-email-guro@fb.com> <1496342115-3974-5-git-send-email-guro@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1496342115-3974-5-git-send-email-guro@fb.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1147 Lines: 31 On Thu, Jun 01, 2017 at 07:35:12PM +0100, Roman Gushchin wrote: > This option defines whether a cgroup should be treated > as a single entity by the OOM killer. > > If set, the OOM killer will compare the whole cgroup with other > memory consumers (other cgroups and tasks in the root cgroup), > and in case of an OOM will kill all belonging tasks. > > Disabled by default. > ... > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > @@ -5265,6 +5292,12 @@ static struct cftype memory_files[] = { > .write = memory_max_write, > }, > { > + .name = "oom_kill_all_tasks", > + .flags = CFTYPE_NOT_ON_ROOT, > + .seq_show = memory_oom_kill_all_tasks_show, > + .write = memory_oom_kill_all_tasks_write, > + }, > + { > .name = "events", > .flags = CFTYPE_NOT_ON_ROOT, > .file_offset = offsetof(struct mem_cgroup, events_file), I don't really like the name of the new knob, but can't come up with anything better :-( May be, drop '_tasks' suffix and call it just 'oom_kill_all'? Or perhaps we should emphasize the fact that this cgroup is treated as a single entity by the OOM killer by calling it 'oom_entity' or 'oom_unit'? Dunno...