[RFC][PATCH 0/3] big chunk memory allocator v2
andi.kleen at intel.com
Fri Oct 29 10:27:41 EDT 2010
On Fri, Oct 29, 2010 at 01:43:51PM +0100, Michał Nazarewicz wrote:
> >>>> (ii) is used only if all other (non-reserved) pages have
> >>>> been allocated.
> >>> That will be near always the case after some uptime, as memory fills up
> >>> with caches. Unless you do early reclaim?
> Hmm... true. Still the point remains that only movable and reclaimable pages are
> allowed in the marked regions. This in effect means that from unmovable pages
> point of view, the area is unusable but I havn't thought of any other way to
> guarantee that because of fragmentation, long sequence of free/movable/reclaimable
> pages is available.
Essentially a movable zone as defined today.
That gets you near all the problems of highmem (except for the mapping
problem and you're a bit more flexible in the splits):
Someone has to decide at boot how much should be movable
and what not, some workloads will run out of space, some may
deadlock when it runs out of management objects, etc.etc.
Classic highmem had a long string of issues with all of this.
If it was an easy problem it had been long solved, but it isn't really.
More information about the linux-arm-kernel