From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx106.postini.com [74.125.245.106]) by kanga.kvack.org (Postfix) with SMTP id 119DD6B0033 for ; Fri, 31 May 2013 07:02:05 -0400 (EDT) Date: Fri, 31 May 2013 13:02:02 +0200 From: Michal Hocko Subject: Re: [patch] mm, memcg: add oom killer delay Message-ID: <20130531110202.GB32491@dhcp22.suse.cz> References: <20130530150539.GA18155@dhcp22.suse.cz> <20130531081052.GA32491@dhcp22.suse.cz> 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 Fri 31-05-13 03:22:59, David Rientjes wrote: > On Fri, 31 May 2013, Michal Hocko wrote: [...] > > > If the oom notifier is in the oom cgroup, it may not be able to > > > successfully read the memcg "tasks" file to even determine the set of > > > eligible processes. > > > > It would have to use preallocated buffer and have mlocked all the memory > > that will be used during oom event. > > > > Wrong, the kernel itself allocates memory when reading this information > and that would fail in an oom memcg. But that memory is not charged to a memcg, is it? So unless you are heading towards global OOM you should be safe. -- 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