Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE

Unmovable allocations in the movable zone. Yuck. Why dont you abandon the 
whole concept of statically sized movable zone and go back to the nice 
earlier idea of dynamically assigning MAX_ORDER chunks to be movable or not?
-
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/

Follow-Ups:
- Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
  - From: Mel Gorman <[email protected]>

References:
- [PATCH 0/8] Create ZONE_MOVABLE to partition memory between movable and non-movable pages
  - From: Mel Gorman <[email protected]>
- [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
  - From: Mel Gorman <[email protected]>

Prev by Date: Re: [PATCH 2.6.20-rc5] Gigaset ISDN driver error handling fixes
Next by Date: Re: [PATCH 05/10] local_t : mips extension
Previous by thread: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE
Next by thread: Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_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]