Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated

On Tue, 5 Dec 2006, Andrew Morton wrote:

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

I'd be glad to make NUMA the default config. That allows us to completely 
get rid of zones. Just keep nodes around. Then we have a DMA node and a 
DMA32 node (working like a headless memory node) and a highmem node.

This would simplify the VM. But please do not have multiple nodes and 
multiple zones. If we do not like the term nodes then lets call them 
zones and get rid of the nodes.
-
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] 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]>
  • Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: -mm merge plans for 2.6.20
• Next by Date: Re: Mounting NFS root FS
• 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):
  • 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]