[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0709111337510.26598@schroedinger.engr.sgi.com>
Date: Tue, 11 Sep 2007 13:41:08 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Jörn Engel <joern@...fs.org>
cc: Nick Piggin <nickpiggin@...oo.com.au>, andrea@...e.de,
torvalds@...ux-foundation.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>,
Mel Gorman <mel@...net.ie>,
William Lee Irwin III <wli@...omorphy.com>,
David Chinner <dgc@....com>,
Jens Axboe <jens.axboe@...cle.com>,
Badari Pulavarty <pbadari@...il.com>,
Maxim Levitsky <maximlevitsky@...il.com>,
Fengguang Wu <fengguang.wu@...il.com>,
swin wang <wangswin@...il.com>, totty.lu@...il.com,
hugh@...itas.com
Subject: Re: [00/41] Large Blocksize Support V7 (adds memmap support)
On Tue, 11 Sep 2007, Jörn Engel wrote:
> What I'm starting to wonder about is where your approach has advantages
> over Andrea's. The chances of triggering something vaguely similar to
> Nick's worst case scenario are certainly higher for your solution. So
> unless there are other upsides it is just the second-best solution.
Nick's worst case scenario is already at least partially addressed by the
Lumpy Reclaim code in 2.6.23. His examples assume 2.6.22 or earlier
code.
The advantages of this approach over Andreas is basically that the 4k
filesystems still can be used as is. 4k is useful for binaries and for
text processing like used for compiles. Large Page sizes are useful for
file systems that contain large datasets (scientific data, multimedia
stuff, databases) for applications that depend on high I/O throughput.
Powered by blists - more mailing lists