Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64

On Mon, 6 Feb 2006, Andi Kleen wrote:

> That is what prereservation was supposed to prevent. I remember there 
> were endless discussions when this all was originally implemented long
> ago (in the version that never got merged).

But the reservation does not consider cpusets and memory policies right?
It surely must fail if one restrict allocation to one node and then we run 
out of memory. That was the testcase that showed the Bus Error....\
-
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:
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
  - From: Andi Kleen <[email protected]>
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
  - From: Christoph Lameter <[email protected]>
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
  - From: Andi Kleen <[email protected]>

Prev by Date: Re: Check for references to discarded sections during build time
Next by Date: Re: Linux drivers management
Previous by thread: Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
Next by thread: Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
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]