Re: Avoiding external fragmentation with a placement policy Version 12

[Mike Kravetz <kravetz@us.ibm.com>]

On Thu, Jun 02, 2005 at 09:56:18AM +1000, Nick Piggin wrote:
> Mike Kravetz wrote:
> >Allocating lots of MAX_ORDER blocks can be very useful for things
> >like hot-pluggable memory.  I know that this may not be of interest
> >to most.  However, I've been combining Mel's defragmenting patch
> >with the memory hotplug patch set.  As a result, I've been able to
> >go from 5GB down to 544MB of memory on my ppc64 system via offline
> >operations.  Note that ppc64 only employs a single (DMA) zone.  So,
> >page 'grouping' based on use is coming mainly from Mel's patch.
> >
> 
> Back in the day, Linus would tell you to take a hike if you
> wanted to complicate the buddy allocator to better support
> memory hotplug ;)
> 
> I don't know what's happened to him now though, he seems to
> have gone a little soft on you enterprise types.
> 
> Seriously - thanks for the data point, I had an idea that you
> guys wanted this for mem hotplug.

Mel wrote the patch independent of the mem hotplug effort.  As
part of the hotplug effort, we knew fragmentation needed to be
addressed.  So, when Mel released his patch we jumped all over
it.

-- 
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/