Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754552AbZA0JbZ (ORCPT ); Tue, 27 Jan 2009 04:31:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752056AbZA0JbQ (ORCPT ); Tue, 27 Jan 2009 04:31:16 -0500 Received: from matrixpower.ru ([195.178.208.66]:45935 "EHLO tservice.net.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751703AbZA0JbP (ORCPT ); Tue, 27 Jan 2009 04:31:15 -0500 Date: Tue, 27 Jan 2009 12:31:05 +0300 From: Evgeniy Polyakov To: David Rientjes Cc: KOSAKI Motohiro , Alan Cox , balbir@linux.vnet.ibm.com, Nikanth Karthikesan , containers@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Torvalds , Arve Hj?nnev?g , Andrew Morton , Chris Snook , Paul Menage Subject: Re: [RFC] [PATCH] Cgroup based OOM killer controller Message-ID: <20090127093105.GB2646@ioremap.net> References: <20090127155825.D476.KOSAKI.MOTOHIRO@jp.fujitsu.com> <20090127164238.D479.KOSAKI.MOTOHIRO@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 857 Lines: 19 On Mon, Jan 26, 2009 at 11:51:27PM -0800, David Rientjes (rientjes@google.com) wrote: > Yeah, I proposed /dev/mem_notify being made as a client of cgroups there > in http://marc.info/?l=linux-kernel&m=123200623628685 > > How do you replace the oom killer's capability of giving a killed task > access to memory reserves with TIF_MEMDIE in userspace? /dev/mem_notify is a great idea, but please do not limit existing oom-killer in its ability to do the job and do not rely on application's ability to send a SIGKILL which will not kill tasks in unkillable state contrary to oom-killer. -- Evgeniy Polyakov -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/