[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1ejm7kndn.fsf@ebiederm.dsl.xmission.com>
Date: Thu, 26 Apr 2007 12:21:24 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: William Lee Irwin III <wli@...omorphy.com>
Cc: Nick Piggin <nickpiggin@...oo.com.au>,
Christoph Lameter <clameter@....com>,
linux-kernel@...r.kernel.org, Mel Gorman <mel@...net.ie>,
David Chinner <dgc@....com>,
Jens Axboe <jens.axboe@...cle.com>,
Badari Pulavarty <pbadari@...il.com>,
Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: [00/17] Large Blocksize Support V3
William Lee Irwin III <wli@...omorphy.com> writes:
> On Thu, Apr 26, 2007 at 05:42:17PM +1000, Nick Piggin wrote:
>> Actually, I don't know why people are so excited about being able to
>> use higher order allocations (I would rather be more excited about
>> never having to use them). But for those few places that really need
>> it, I'd rather see them use a virtually mapped kernel with proper
>> defragmentation rather than putting hacks all through the core code.
>
> In memory as on disk, contiguity matters a lot for performance.
Not nearly so much though. In memory you don't have seeks to avoid.
On disks avoiding seeks is everything.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists