[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070712122925.192a6601.akpm@linux-foundation.org>
Date: Thu, 12 Jul 2007 12:29:25 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: mel@...net.ie (Mel Gorman)
Cc: npiggin@...e.de, kenchen@...gle.com, jschopp@...tin.ibm.com,
apw@...dowen.org, kamezawa.hiroyu@...fujitsu.com,
a.p.zijlstra@...llo.nl, y-goto@...fujitsu.com, clameter@....com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans -- anti-fragmentation
On Tue, 10 Jul 2007 11:20:43 +0100
mel@...net.ie (Mel Gorman) wrote:
> > create-the-zone_movable-zone.patch
> > allow-huge-page-allocations-to-use-gfp_high_movable.patch
> > handle-kernelcore=-generic.patch
> >
> > Mel's moveable-zone work. In a similar situation. We need to stop whatever
> > we're doing and get down and work out what we're going to do with all this
> > stuff.
> >
>
> Whatever about grouping pages by mobility, I would like to see these go
> through. They have a real application for hugetlb pool resizing where the
> administrator knows the range of hugepages that will be required but doesn't
> want to waste memory when the required number of hugepages is small. I've
> cc'd Kenneth Chen as I believe he has run into this problem recently where
> I believe partitioning memory would have helped. He'll either confirm or deny.
Still no decision here, really.
Should we at least go for
add-__gfp_movable-for-callers-to-flag-allocations-from-high-memory-that-may-be-migrated.patch
create-the-zone_movable-zone.patch
allow-huge-page-allocations-to-use-gfp_high_movable.patch
handle-kernelcore=-generic.patch
in 2.6.23?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists