[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070714082807.GC1198@wotan.suse.de>
Date: Sat, 14 Jul 2007 10:28:07 +0200
From: Nick Piggin <npiggin@...e.de>
To: Mel Gorman <mel@...net.ie>
Cc: Andrew Morton <akpm@...ux-foundation.org>, 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: [PATCH] Add a movablecore= parameter for sizing ZONE_MOVABLE
On Fri, Jul 13, 2007 at 04:56:10PM +0100, Mel Gorman wrote:
> On (12/07/07 22:32), Mel Gorman didst pronounce:
>
> > > 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?
> >
> > Well, yes please from me obviously :) . There is one additional patch
> > I would like to send on tomorrow and that is providing the movablecore=
>
> This is the patch. It has been boot-tested on a number of machines and
> behaves as expected. Nick, with this in addition, do you have any
> objection to the ZONE_MOVABLE patches going through to 2.6.23?
What's the status of making it configurable? I didn't see something
in -mm for that yet?
But that's not as important as ensuring the concept and user visible
stuff is in good shape, which I no longer have any problems with. So
yeah I think it would be good to get this in and get people up and
running with it.
-
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