Re: [PATCH 2/5] Light Fragmentation Avoidance V20: 002_usemap
From: Mel Gorman
Date: Tue Nov 22 2005 - 05:20:32 EST
On Tue, 22 Nov 2005, Andy Whitcroft wrote:
> Mel Gorman wrote:
> > That's iterating through, potentially, 1024 pages which I considered too
> > expensive. In terms of code complexity, the page-flags patch adds 237
> > which is not much of a saving in comparison to 275 that the usemap
> > approach uses.
> Surley you would just use a single bit in the first page of a MAX_ORDER
No, because you need the flag at free time to determine what list is
should be going to. There is no guarantee that the first page remains
allocated or that it has not been used for fallback.
> We guarentee that the mem_map is contigious out to MAX_ORDER
> pages so you can simply calculate the offset. The page free path does
> the same thing to find the buddy pages when coallescing.
That's finding buddies, not finding the first page in the MAX_ORDER block.
I revisited the page-flag approach anyway and got it working properly. It
currently stands at 160 code insertions. It's been run through benchmarks
at the moment.
> > Again, I can revisit the page-flag approach if I thought that something
> > like this would get merged and people would not choke on another page flag
> > being consumed.
> All of that said, I am not even sure we have a bit left in the page
> flags on smaller architectures :/.
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@xxxxxxxxxx For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>
Part-time Phd Student Java Applications Developer
University of Limerick IBM Dublin Software Lab
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/