Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754641AbZA0Jix (ORCPT ); Tue, 27 Jan 2009 04:38:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751470AbZA0Jio (ORCPT ); Tue, 27 Jan 2009 04:38:44 -0500 Received: from smtp-out.google.com ([216.239.45.13]:59481 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751328AbZA0Jin (ORCPT ); Tue, 27 Jan 2009 04:38:43 -0500 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:user-agent:mime-version:content-type:x-gmailtapped-by:x-gmailtapped; b=SV9JfgsI3KszQi+SFpeQKTHRSSUy7FFB4TygN/iJVLQ0dcjFf5UGNAelXSWVL18z7 IMQHx+MnePQ3twOE4o9Iw== Date: Tue, 27 Jan 2009 01:37:55 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Evgeniy Polyakov 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 In-Reply-To: <20090127093105.GB2646@ioremap.net> Message-ID: References: <20090127155825.D476.KOSAKI.MOTOHIRO@jp.fujitsu.com> <20090127164238.D479.KOSAKI.MOTOHIRO@jp.fujitsu.com> <20090127093105.GB2646@ioremap.net> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-GMailtapped-By: 172.25.146.75 X-GMailtapped: rientjes Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1089 Lines: 25 On Tue, 27 Jan 2009, Evgeniy Polyakov wrote: > /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. > You're missing the point, /dev/mem_notify would notify userspace of lowmem situations and allow it to respond appropriately in any number of ways before an oom condition exists. When the system (or cpuset, memory controller, etc) is oom, userspace can choose to defer to the oom killer so that it may kill a task that would most likely lead to future memory freeing with access to memory reserves. There is no additional oom killer limitation imposed here, nor can the oom killer kill a task hung in D state any better than userspace. Thanks. -- 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/