From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) by kanga.kvack.org (Postfix) with ESMTP id B39346B0035 for ; Mon, 18 Nov 2013 13:52:20 -0500 (EST) Received: by mail-pb0-f48.google.com with SMTP id md12so687422pbc.7 for ; Mon, 18 Nov 2013 10:52:20 -0800 (PST) Received: from psmtp.com ([74.125.245.148]) by mx.google.com with SMTP id qj1si10357017pbc.84.2013.11.18.10.52.17 for ; Mon, 18 Nov 2013 10:52:18 -0800 (PST) Received: by mail-ea0-f180.google.com with SMTP id f15so879018eak.39 for ; Mon, 18 Nov 2013 10:52:15 -0800 (PST) Date: Mon, 18 Nov 2013 19:52:13 +0100 From: Michal Hocko Subject: Re: [patch 2/2] mm, memcg: add memory.oom_control notification for system oom Message-ID: <20131118185213.GA12923@dhcp22.suse.cz> References: <20131031054942.GA26301@cmpxchg.org> <20131113233419.GJ707@cmpxchg.org> <20131114032508.GL707@cmpxchg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: David Rientjes Cc: Andrew Morton , Johannes Weiner , KAMEZAWA Hiroyuki , linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org On Thu 14-11-13 15:26:55, David Rientjes wrote: > A subset of applications that wait on memory.oom_control don't disable > the oom killer for that memcg and simply log or cleanup after the kernel > oom killer kills a process to free memory. > > We need the ability to do this for system oom conditions as well, i.e. > when the system is depleted of all memory and must kill a process. For > convenience, this can use memcg since oom notifiers are already present. Using the memcg interface for "read-only" interface without any plan for the "write" is only halfway solution. We want to handle global OOM in a more user defined ways but we have to agree on the proper interface first. I do not want to end up with something half baked with memcg and a different interface to do the real thing just because memcg turns out to be unsuitable. And to be honest, the more I am thinking about memcg based interface the stronger is my feeling that it is unsuitable for the user defined OOM policies. But that should be discussed properly (I will send a RFD in the follow up days). [...] -- Michal Hocko SUSE Labs -- 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: email@kvack.org