Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK

On Mon, 6 Aug 2007, Daniel Phillips wrote:

> Currently your system likely would have died here, so ending up with a 
> reserve page temporarily on the wrong node is already an improvement. 

The system would have died? Why? The application in the cpuset that 
ran out of memory should have died not the system.
-
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 02/10] mm: system wide ALLOC_NO_WATERMARK
    • From: Daniel Phillips <[email protected]>

• References:
  • [PATCH 00/10] foundations for reserve-based allocation
    • From: Peter Zijlstra <[email protected]>
  • [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
    • From: Peter Zijlstra <[email protected]>
  • Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
    • From: Christoph Lameter <[email protected]>
  • Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
    • From: Daniel Phillips <[email protected]>

• Prev by Date: Re: [patch] radix-tree: use indirect bit
• Next by Date: Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
• Previous by thread: Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
• Next by thread: Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK
• 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]