Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE

On Mon, 6 Aug 2007, Andrew Morton wrote:

> 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?

Take the horrible hack for .23.

For .24 either merge the mobility or get the other solution that Mel is 
working on. That solution would only use a single zonelist per node and 
filter on the fly. That may help performance and also help to make memory 
policies work better.
-
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/

---

• References:
  • [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE
    • From: [email protected] (Mel Gorman)
  • Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
• Next by Date: Re: OOPS in shrink_dcache_for_umount
• Previous by thread: Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE
• Next by thread: Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE
• Index(es):
  • Date
  • Thread

[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]