Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761232AbXIRRa2 (ORCPT ); Tue, 18 Sep 2007 13:30:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760073AbXIRR3t (ORCPT ); Tue, 18 Sep 2007 13:29:49 -0400 Received: from smtp102.mail.mud.yahoo.com ([209.191.85.212]:23363 "HELO smtp102.mail.mud.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1759817AbXIRR3p (ORCPT ); Tue, 18 Sep 2007 13:29:45 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Disposition:Message-Id:Content-Type:Content-Transfer-Encoding; b=Md4NnfbSuLktti9cIZ4ZwkCLJtr/lfU3G6FLgJr9ID8RAyGJJTqTjdYxLLtesL9ZkXeSswhrWOf25tKdp4dnHWKwyt+ZNVo3mjawEy1DPSrjYHOtQREyoPl+yvo72rsGDUk+k5vveeJm1FEYgYOuovOFPr5cnBo/VKIbEPcKh3c= ; X-YMail-OSG: BzQzaA8VM1mnBVEtOiufhEhh.vbVPWva1xisWmIBV0kM9KV1sRX1pzDN6XjPUEApMKXmeRIJug-- From: Nick Piggin To: Christoph Lameter Subject: Re: [00/41] Large Blocksize Support V7 (adds memmap support) Date: Tue, 18 Sep 2007 10:11:17 +1000 User-Agent: KMail/1.9.5 Cc: Mel Gorman , Goswin von Brederlow , Andrew Morton , Joern Engel , andrea@suse.de, torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Christoph Hellwig , William Lee Irwin III , David Chinner , Jens Axboe , Badari Pulavarty , Maxim Levitsky , Fengguang Wu , swin wang , totty.lu@gmail.com, hugh@veritas.com References: <20070911060349.993975297@sgi.com> <200709161903.37295.nickpiggin@yahoo.com.au> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200709181011.17975.nickpiggin@yahoo.com.au> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 914 Lines: 18 On Tuesday 18 September 2007 08:00, Christoph Lameter wrote: > On Sun, 16 Sep 2007, Nick Piggin wrote: > > I don't know how it would prevent fragmentation from building up > > anyway. It's commonly the case that potentially unmovable objects > > are allowed to fill up all of ram (dentries, inodes, etc). > > Not in 2.6.23 with ZONE_MOVABLE. Unmovable objects are not allocated from > ZONE_MOVABLE and thus the memory that can be allocated for them is > limited. Why would ZONE_MOVABLE require that "movable objects should be moved out of the way for unmovable ones"? It never _has_ any unmovable objects in it. Quite obviously we were not talking about reserve zones. - 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/