On Mon, 6 Aug 2007, Andrew Morton wrote: > Plus I don't think there are many flags left in the upper 32-bits. ia64 > swooped in and gobbled lots of them, although it's not immediately clear > how many were consumed. IA64 uses one of these bits for the uncached allocator. 10 bits used for the node. Sparsemem may use some of the rest. - 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 00/10] foundations for reserve-based allocation
- From: Peter Zijlstra <[email protected]>
- [PATCH 03/10] mm: tag reseve pages
- From: Peter Zijlstra <[email protected]>
- Re: [PATCH 03/10] mm: tag reseve pages
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 03/10] mm: tag reseve pages
- From: Andi Kleen <[email protected]>
- Re: [PATCH 03/10] mm: tag reseve pages
- From: Christoph Lameter <[email protected]>
- Re: [PATCH 03/10] mm: tag reseve pages
- From: Peter Zijlstra <[email protected]>
- Re: [PATCH 03/10] mm: tag reseve pages
- From: Andi Kleen <[email protected]>
- Re: [PATCH 03/10] mm: tag reseve pages
- From: Andrew Morton <[email protected]>
- [PATCH 00/10] foundations for reserve-based allocation
- Prev by Date: Re: Disk spin down issue on shut down/suspend to disk
- Next by Date: Re: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE
- Previous by thread: Re: [PATCH 03/10] mm: tag reseve pages
- Next by thread: Re: [PATCH 03/10] mm: tag reseve pages
- Index(es):
 |