[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070426145310.GH19966@holomorphy.com>
Date: Thu, 26 Apr 2007 07:53:10 -0700
From: William Lee Irwin III <wli@...omorphy.com>
To: Nick Piggin <nickpiggin@...oo.com.au>
Cc: Christoph Lameter <clameter@....com>,
"Eric W. Biederman" <ebiederm@...ssion.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
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.
On Thu, Apr 26, 2007 at 05:42:17PM +1000, Nick Piggin wrote:
> I don't think that it is solved, and I think the heuristics that are
> there would be put under more stress if they become widely used. And
> it isn't only about whether we can get the page or not, but also about
> the cost. Look up Linus's arguments about page colouring, which are
> similar and I also think are pretty valid.
Perhaps broader exposure would help demonstrate their efficacy, or
otherwise discover what deficits need to be addressed.
-- wli
-
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