From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753171AbaCFVPO (ORCPT ); Thu, 6 Mar 2014 16:15:14 -0500 Received: from mail-qg0-f45.google.com ([209.85.192.45]:40831 "EHLO mail-qg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752078AbaCFVPL (ORCPT ); Thu, 6 Mar 2014 16:15:11 -0500 Date: Thu, 6 Mar 2014 16:15:06 -0500 From: Tejun Heo To: David Rientjes Cc: Andrew Morton , Johannes Weiner , Michal Hocko , KAMEZAWA Hiroyuki , Christoph Lameter , Pekka Enberg , Mel Gorman , Oleg Nesterov , Rik van Riel , Jianguo Wu , Tim Hockin , linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [patch 10/11] mm, memcg: add memory.oom_control notification for system oom Message-ID: <20140306211506.GD17902@htj.dyndns.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 04, 2014 at 07:59:41PM -0800, David Rientjes wrote: > Now that process handling system oom conditions have access to a small > amount of memory reserves, we need a way to notify those process on > system oom conditions. > > When a userspace process waits on the root memcg's memory.oom_control, it > will wake up anytime there is a system oom condition. > > This is a special case of oom notifiers since it doesn't subsequently > notify all memcgs under the root memcg (all memcgs on the system). We > don't want to trigger those oom handlers which are set aside specifically > for true memcg oom notifications that disable their own oom killers to > enforce their own oom policy, for example. > > Signed-off-by: David Rientjes Until consensus on the whole approach can be reached, Nacked-by: Tejun Heo Thanks. -- tejun