> The only way to support big areas is to have special zones for them. > > (Then, we may be able to use the special zones for small things too, but > under special rules, like "only used for anonymous mappings" where we > can just always remove them by paging them out. But it would still be a > special area meant for big pages, just temporarily "on loan"). The problem is how these zones get resized. Can we hotplug memory between them, with some sparsemem like indirection layer? Real customers have shown us that their workloads shift, and they have different needs at different parts of the day. We can't just pick one size and call it good. It's the same argument as the traditional VM balancing act between pagecache, user pages, and kernel pages (which incidentally, we don't use zones for). We want the system to be able to use memory wherever it's most needed. M. - 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: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Linus Torvalds <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- References:
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Ingo Molnar <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Dave Hansen <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Ingo Molnar <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Dave Hansen <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Ingo Molnar <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Dave Hansen <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Dave Hansen <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Nick Piggin <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: "Martin J. Bligh" <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Nick Piggin <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: "Martin J. Bligh" <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Arjan van de Ven <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Linus Torvalds <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Mel Gorman <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- From: Linus Torvalds <[email protected]>
- Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- Prev by Date: Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- Next by Date: Re: [Patch] add AOP_TRUNCATED_PAGE, prepend AOP_ to WRITEPAGE_ACTIVATE
- Previous by thread: Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- Next by thread: Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
- Index(es):