On Mon, 6 Aug 2007 22:55:41 +0100 [email protected] (Mel Gorman) wrote:
> On (06/08/07 22:31), Andi Kleen didst pronounce:
> >
> > > If correct, I would suggest merging the horrible hack for .23 then taking
> > > it out when we merge "grouping pages by mobility". But what if we don't do
> > > that merge?
> >
> > Or disable ZONE_MOVABLE until it is usable?
>
> It's usable now. The issue with policies only occurs if the user specifies
> kernelcore= or movablecore= on the command-line. Your language suggests
> that you believe policies are not applied when ZONE_MOVABLE is configured
> at build-time.
So.. the problem which we're fixing here is only present when someone
use kernelcore=. This is in fact an argument for _not_ merging the
horrible-hack.
How commonly do we expect people to specify kernelcore=? If "not much" then
it isn't worth adding the __alloc_pages() overhead?
(It's a pretty darn small overhead, I must say)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
