On Fri, 25 Jan 2002, Phil Thompson wrote:
>> The first question is: has anybody already done this? Particularly as,
>> once you've identified where the holes are, the code isn't board
On Fri, Jan 25, 2002 at 02:20:33PM -0700, Jason Gunthorpe wrote:
> Is this of any help?
> William Irwin [*] announced:
> A number of people have expressed a wish to replace the bitmap-based
> bootmem allocator with one that tracks ranges explicitly. I have written
> such a replacement in order to deal with some of the situations I have
I ran into some code acceptance issues in three places:
(1) I used trees
(2) I didn't go about changing the arch-specific code to
actually simplify the calling sequence as it appeared
in arch-specific code.
(3) it is a whole-hog rewrite of bootmem.c, which perhaps attracted
flak from the original author
The last bits of this I released are in:
I'm not sure it addresses all the issues that arise here -- largely
it just avoids some code complexity in laying out the bootmem bitmaps.
DISCONTIGMEM as I understand it just minimally adjusts the core bootmem
so it can handle things at all, and then focuses on the actual hard
parts needed for things to work well on larger systems.
(Of course, that's an extremely vague description of the difference, but
I won't go about reciting featuresets aside from this high-level stuff.)