From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx163.postini.com [74.125.245.163]) by kanga.kvack.org (Postfix) with SMTP id B4EF76B004A for ; Tue, 13 Mar 2012 12:51:40 -0400 (EDT) Date: Tue, 13 Mar 2012 17:51:18 +0100 From: Johannes Weiner Subject: Re: [patch] mm, memcg: do not allow tasks to be attached with zero limit Message-ID: <20120313165117.GA1708@cmpxchg.org> References: <20120308122951.2988ec4e.akpm@linux-foundation.org> <20120309102255.bbf94164.kamezawa.hiroyu@jp.fujitsu.com> <20120308173818.ae5f621b.akpm@linux-foundation.org> <20120309105706.4001646a.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120309105706.4001646a.kamezawa.hiroyu@jp.fujitsu.com> Sender: owner-linux-mm@kvack.org List-ID: To: KAMEZAWA Hiroyuki Cc: Andrew Morton , David Rientjes , Michal Hocko , Balbir Singh , cgroups@vger.kernel.org, linux-mm@kvack.org On Fri, Mar 09, 2012 at 10:57:06AM +0900, KAMEZAWA Hiroyuki wrote: > On Thu, 8 Mar 2012 17:38:18 -0800 > Andrew Morton wrote: > > > On Fri, 9 Mar 2012 10:22:55 +0900 KAMEZAWA Hiroyuki wrote: > > > > > On Thu, 8 Mar 2012 12:29:51 -0800 > > > Andrew Morton wrote: > > > > > > > On Wed, 7 Mar 2012 19:14:49 -0800 (PST) > > > > David Rientjes wrote: > > > > > > > > > This patch prevents tasks from being attached to a memcg if there is a > > > > > hard limit of zero. > > > > > > > > We're talking about the memcg's limit_in_bytes here, yes? > > > > > > > > > Additionally, the hard limit may not be changed to > > > > > zero if there are tasks attached. > > > > > > > > hm, well... why? That would be user error, wouldn't it? What is > > > > special about limit_in_bytes=0? The memcg will also be unviable if > > > > limit_in_bytes=1, but we permit that. > > > > > > > > IOW, confused. > > > > > > > Ah, yes. limit_in_bytes < some small size can cause the same trouble. > > > Hmm... should we have configurable min_limit_in_bytes as sysctl or root memcg's > > > attaribute.. ? > > > > Why do *anything*? If the operator chose an irrational configuration > > then things won't work correctly and the operator will then fix the > > configuration? > > > > Because the result of 'error operaton' is SIGKILL to a task, which may be > owned by very importang customer of hosting service. > > Isn't this severe punishment for error operation ? > > Considering again, I have 2 thoughts. > > - it should be guarded by MiddleWare, it's not kernel job ! > - memcg should be more easy-to-use, friendly to users. > > If the result is just an error as EINVAL or EBUSY, I may not be nervous.... You can still disable the OOM killer. If you don't, you can always get killed, so I'm not convinced by this patch or a sysctl, either. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org