From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Bharata B Rao <bharata@in.ibm.com>,
Ray Bryant <raybry@mpdtxmail.amd.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
Date: Wed, 8 Feb 2006 16:45:24 +0100 [thread overview]
Message-ID: <200602081645.24733.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0602080736510.908@schroedinger.engr.sgi.com>
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
>
next prev parent reply other threads:[~2006-02-08 15:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060205163618.GB21972@in.ibm.com>
2006-02-05 17:03 ` [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64 Andi Kleen
2006-02-06 16:11 ` Christoph Lameter
2006-02-06 18:12 ` Andi Kleen
2006-02-06 18:25 ` Christoph Lameter
2006-02-06 18:31 ` Andi Kleen
2006-02-06 18:45 ` Christoph Lameter
2006-02-06 18:55 ` Andi Kleen
2006-02-06 19:22 ` Christoph Lameter
2006-02-07 5:59 ` Bharata B Rao
2006-02-07 16:49 ` Christoph Lameter
2006-02-07 23:27 ` Ray Bryant
2006-02-07 23:36 ` Andi Kleen
2006-02-08 12:10 ` Bharata B Rao
2006-02-08 15:42 ` Christoph Lameter
2006-02-08 15:45 ` Andi Kleen [this message]
2006-02-08 15:59 ` Christoph Lameter
2006-02-08 16:06 ` Andi Kleen
2006-02-08 16:20 ` Christoph Lameter
2006-02-08 16:27 ` Andi Kleen
2006-02-08 16:51 ` Christoph Lameter
2006-02-09 4:39 ` Bharata B Rao
2006-02-09 9:58 ` Andi Kleen
2006-02-14 19:33 ` Christoph Lameter
2006-02-15 5:46 ` Bharata B Rao
2006-02-15 10:38 ` Bharata B Rao
2006-02-15 11:21 ` Andi Kleen
2006-02-15 18:14 ` Christoph Lameter
2006-02-16 5:18 ` Bharata B Rao
2006-02-15 18:10 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602081645.24733.ak@suse.de \
--to=ak@suse.de \
--cc=bharata@in.ibm.com \
--cc=clameter@engr.sgi.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raybry@mpdtxmail.amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.