Re: Nasty Evil Memory Fragmentation fix

[Alexandre Julliard]

Ove Kaaven  writes:
> Well, after looking at some allocator algorithms, it seems to me there's
> no reason to change neither the bin sizes nor the data structures. We just
> have to change the free block selection algorithm - from my reading of the
> code, right now it seems to always choose the *newest* (most recently
> added) free block that's big enough. By changing it to always choose the
> *oldest* free block instead, we'd already have a huge improvement.
> (That's essentially the effect of Gav's patch, but only for big blocks,
> but I suspect that could safely be done for *all* block sizes)

I don't think that's a good idea. It's pretty bad for the cache and
paging system to reuse oldest blocks first.