Re: [PATCH] change global zonelist order on NUMA v3

Hmmmm... One additional easy way to fix this would be to create a DMA 
node and place it very distant to other nodes. This would make it a 
precious system resource that is only used for

1. GFP_DMA allocations

2. If the memory on the other nodes is exhausted.

-
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] change global zonelist order on NUMA v3
    • From: Lee Schermerhorn <[email protected]>

• References:
  • [PATCH] change global zonelist order on NUMA v2
    • From: KAMEZAWA Hiroyuki <[email protected]>
  • Re: [PATCH] change global zonelist order on NUMA v2
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH] change global zonelist order on NUMA v2
    • From: KAMEZAWA Hiroyuki <[email protected]>
  • [PATCH] change global zonelist order on NUMA v3
    • From: KAMEZAWA Hiroyuki <[email protected]>
  • Re: [PATCH] change global zonelist order on NUMA v3
    • From: Lee Schermerhorn <[email protected]>

• Prev by Date: Re: [patch] CFS scheduler, -v6
• Next by Date: Re: [00/17] Large Blocksize Support V3
• Previous by thread: Re: [PATCH] change global zonelist order on NUMA v3
• Next by thread: Re: [PATCH] change global zonelist order on NUMA v3
• 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]