From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S932371AbdIGQV2 (ORCPT <rfc822;w@1wt.eu>);
        Thu, 7 Sep 2017 12:21:28 -0400
Received: from resqmta-ch2-01v.sys.comcast.net ([69.252.207.33]:38790 "EHLO
        resqmta-ch2-01v.sys.comcast.net" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S932083AbdIGQVY (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 7 Sep 2017 12:21:24 -0400
Date: Thu, 7 Sep 2017 11:21:22 -0500 (CDT)
From: Christopher Lameter <cl@linux.com>
X-X-Sender: cl@nuc-kabylake
To: Michal Hocko <mhocko@kernel.org>
cc: Roman Gushchin <guro@fb.com>, linux-mm@kvack.org,
        Vladimir Davydov <vdavydov.dev@gmail.com>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
        David Rientjes <rientjes@google.com>,
        Andrew Morton <akpm@linux-foundation.org>, Tejun Heo <tj@kernel.org>,
        kernel-team@fb.com, cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [v7 5/5] mm, oom: cgroup v2 mount option to disable cgroup-aware
 OOM killer
In-Reply-To: <20170905151251.luh4wogjd3msfqgf@dhcp22.suse.cz>
Message-ID: <alpine.DEB.2.20.1709071120020.20082@nuc-kabylake>
References: <20170904142108.7165-1-guro@fb.com> <20170904142108.7165-6-guro@fb.com> <20170905134412.qdvqcfhvbdzmarna@dhcp22.suse.cz> <20170905143021.GA28599@castle.dhcp.TheFacebook.com> <20170905151251.luh4wogjd3msfqgf@dhcp22.suse.cz>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-CMAE-Envelope: MS4wfIf+oRiU2fIcKk6b9+u1217obqqRag8yUoyk7JC2OT6e1zwoMWWHpyxw62yD6bWanwKFHR9MXPgwHfKg+pz5/bOarz2W8860RTAP5E6j+qSM/IK6R+vr
 SVEZzXTv7J6g8NdJRtJofPtOWqiWyJybI9egly9ID0Ih/GfzYMRIJJBcpzaTN7DyQeMp8qaQeCwX0rCfklHyrt2xcqAm3GD8rcriLZgVy84yQpDzyKHMYqA+
 DothuC5YPYA1NMbEIBxLsYcV6AtKokNJI4SkKs4KIJyuzitn9HNSplEeutoglCO/IoA2uDxxFyfP7Gj6V2ToxaFK/W0oMwYfQ+54tKxFBsgkhHUsXoDWnvyT
 O+A8XmaTSDvzXsyMT3hR4FvhPmwXZA6HEAbWCiG+RwcLJNvLl0sxT0Xv+88qMKa8xOKhHShfeqsZOx86FSGr8RqwhEH7Pz8nFb2gwKSLlAYRPTUzA57L8PjX
 1eTbnEDXFo3LAXF0YtwOsRhAbwpU4IoKsjsZKjO0VV8uDxhECapE3tNGCh3T/0lradQu9yPnWLVff30n
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 5 Sep 2017, Michal Hocko wrote:

> I would argue that we should simply deprecate and later drop the sysctl.
> I _strongly_ suspect anybody is using this. If yes it is not that hard
> to change the kernel command like rather than select the sysctl. The
> deprecation process would be
> 	- warn when somebody writes to the sysctl and check both boot
> 	  and sysctl values
> 	[ wait some time ]
> 	- keep the sysctl but return EINVAL
> 	[ wait some time ]
> 	- remove the sysctl

Note that the behavior that would be enabled by the sysctl is the default
behavior for the case of a constrained allocation. If a process does an
mbind to numa node 3 and it runs out of memory then that process should be
killed and the rest is fine.