From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with ESMTP id 133E96B01E3 for ; Thu, 22 Apr 2010 03:23:32 -0400 (EDT) Date: Thu, 22 Apr 2010 17:23:19 +1000 From: Nick Piggin Subject: Re: [patch -mm] memcg: make oom killer a no-op when no killable task can be found Message-ID: <20100422072319.GW5683@laptop> References: <20100407092050.48c8fc3d.kamezawa.hiroyu@jp.fujitsu.com> <20100407205418.FB90.A69D9226@jp.fujitsu.com> <20100421121758.af52f6e0.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100421121758.af52f6e0.akpm@linux-foundation.org> Sender: owner-linux-mm@kvack.org To: Andrew Morton Cc: David Rientjes , KOSAKI Motohiro , KAMEZAWA Hiroyuki , anfei , nishimura@mxp.nes.nec.co.jp, Balbir Singh , linux-mm@kvack.org List-ID: On Wed, Apr 21, 2010 at 12:17:58PM -0700, Andrew Morton wrote: > > fyi, I still consider these patches to be in the "stuck" state. So we > need to get them unstuck. > > > Hiroyuki (and anyone else): could you please summarise in the briefest > way possible what your objections are to Daivd's oom-killer changes? > > I'll start: we don't change the kernel ABI. Ever. And when we _do_ > change it we don't change it without warning. How is this turning into such a big issue? It is totally ridiculous. It is not even a "cleanup". Just drop the ABI-changing patches, and I think the rest of them looked OK, didn't they? -- 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