Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757590AbXHJDs3 (ORCPT ); Thu, 9 Aug 2007 23:48:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752337AbXHJDsU (ORCPT ); Thu, 9 Aug 2007 23:48:20 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:59376 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750736AbXHJDsT (ORCPT ); Thu, 9 Aug 2007 23:48:19 -0400 Date: Thu, 9 Aug 2007 20:48:16 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Daniel Phillips cc: Daniel Phillips , Peter Zijlstra , Matt Mackall , linux-kernel@vger.kernel.org, linux-mm@kvack.org, David Miller , Andrew Morton , Daniel Phillips Subject: Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK In-Reply-To: <4a5909270708092034yaa0a583w70084ef93266df48@mail.gmail.com> Message-ID: References: <20070806102922.907530000@chello.nl> <200708061649.56487.phillips@phunq.net> <4a5909270708080037n32be2a73k5c28d33bb02f770b@mail.gmail.com> <4a5909270708091141tb259eddyb2bba1270751ef1@mail.gmail.com> <4a5909270708091717n2f93fcb5i284d82edfd235145@mail.gmail.com> <4a5909270708092034yaa0a583w70084ef93266df48@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 696 Lines: 16 On Thu, 9 Aug 2007, Daniel Phillips wrote: > If you believe that the deadlock problems we address here can be > better fixed by making reclaim more intelligent then please post a > patch and we will test it. I am highly skeptical, but the proof is in > the patch. Then please test the patch that I posted here earlier to reclaim even if PF_MEMALLOC is set. It may require some fixups but it should address your issues in most vm load situations. - 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/