[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0708071334430.3430@schroedinger.engr.sgi.com>
Date: Tue, 7 Aug 2007 13:37:24 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Mel Gorman <mel@...net.ie>, Andi Kleen <ak@...e.de>,
Lee.Schermerhorn@...com, kamezawa.hiroyu@...fujitsu.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Apply memory policies to top two highest zones when
highest zone is ZONE_MOVABLE
On Tue, 7 Aug 2007, Andrew Morton wrote:
> > It's even more constrained than that. It only applies to the MPOL_BIND
> > policy when kernelcore= is specified. The other policies work the same
> > as they ever did.
>
> so.. should we forget about merging the horrible-hack?
Support MPOL_BIND is a basic NUMA feature. This is going to make .23
unusable for us if kernelcore= is used. If we cannot use kernelcore then
NUMA systems cannot use the features that depend on kernelcore.
-
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