Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932206AbXAQJ5x (ORCPT ); Wed, 17 Jan 2007 04:57:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932209AbXAQJ5x (ORCPT ); Wed, 17 Jan 2007 04:57:53 -0500 Received: from smtp.osdl.org ([65.172.181.24]:56935 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932206AbXAQJ5w (ORCPT ); Wed, 17 Jan 2007 04:57:52 -0500 Date: Wed, 17 Jan 2007 01:57:34 -0800 From: Andrew Morton To: Paul Jackson Cc: clameter@sgi.com, menage@google.com, linux-kernel@vger.kernel.org, nickpiggin@yahoo.com.au, linux-mm@kvack.org, ak@suse.de, dgc@sgi.com Subject: Re: [RFC 0/8] Cpuset aware writeback Message-Id: <20070117015734.b74f8a6b.akpm@osdl.org> In-Reply-To: <20070117000158.a2e7016e.pj@sgi.com> References: <20070116054743.15358.77287.sendpatchset@schroedinger.engr.sgi.com> <20070116135325.3441f62b.akpm@osdl.org> <20070116154054.e655f75c.akpm@osdl.org> <20070116170734.947264f2.akpm@osdl.org> <20070116183406.ed777440.akpm@osdl.org> <20070116200506.d19eacf5.akpm@osdl.org> <20070116230034.b8cb4263.akpm@osdl.org> <20070117000158.a2e7016e.pj@sgi.com> X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.19; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1129 Lines: 25 > On Wed, 17 Jan 2007 00:01:58 -0800 Paul Jackson wrote: > Andrew wrote: > > - consider going off-cpuset for critical allocations. > > We do ... in mm/page_alloc.c: > > * This is the last chance, in general, before the goto nopage. > * Ignore cpuset if GFP_ATOMIC (!wait) rather than fail alloc. > * See also cpuset_zone_allowed() comment in kernel/cpuset.c. > */ > page = get_page_from_freelist(gfp_mask, order, zonelist, alloc_flags); > > We also allow GFP_KERNEL requests to escape the current cpuset, to the nearest > enclosing mem_exclusive cpuset, which is typically a big cpuset covering most > of the system. hrm. So how come NFS is getting oom-killings? The oom-killer normally spews lots of useful stuff, including backtrace. For some reason that's not coming out for Christoph. Log facility level, perhaps? - 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/