On Tue, 5 Dec 2006 08:05:16 -0800 (PST) Christoph Lameter <[email protected]> wrote: > On Tue, 5 Dec 2006, Mel Gorman wrote: > > > That is one possibility. There are people working on fake nodes for containers > > at the moment. If that pans out, the infrastructure would be available to > > create one node per DIMM. > > Right that is a hack in use for one project. Other projects can use it too. It has the distinct advantage that it works with today's VM. > We would be adding huge > amounts of VM overhead if we do a node per DIMM. No we wouldn't. > So a desktop system with two dimms is to be treated like a NUMA > system? Could do that. Or make them separate zones. > Or how else do we deal with the multitude of load balancing > situations that the additional nodes will generate? No such problems are known. - 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] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Christoph Lameter <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- References:
- [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: [email protected] (Mel Gorman)
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Mel Gorman <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: [email protected] (Mel Gorman)
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Mel Gorman <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Mel Gorman <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Mel Gorman <[email protected]>
- Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- From: Christoph Lameter <[email protected]>
- [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- Prev by Date: Re: -mm merge plans for 2.6.20
- Next by Date: Re: 2.6.19 git compile error - "current_is_keventd" [drivers/net/phy/libphy.ko] undefined
- Previous by thread: Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- Next by thread: Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
- Index(es):