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

On Wednesday 08 February 2006 16:42, Christoph Lameter wrote:

> However, this has implications for policy_zone. This variable should store
> the zone that policies apply to. However, in your case this zone will vary 
> which may lead to all sorts of weird behavior even if we fix 
> bind_zonelist. To which zone does policy apply? ZONE_NORMAL or ZONE_DMA32?

It really needs to apply to both (currently you can't police 4GB of your 
memory on x86-64) But I haven't worked out a good design how to implement it yet.

-Andi


> 
-
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: [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]>

• References:
  • Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
    • From: Bharata B Rao <[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]>

• Prev by Date: Re: libata PATA status report on 2.6.16-rc1-mm5
• Next by Date: Re: [SCSI] fix wrong context bugs in SCSI
• 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]