From: Nick Piggin <npiggin@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andi Kleen <ak@suse.de>, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [rfc] balance-on-fork NUMA placement
Date: Fri, 3 Aug 2007 03:14:48 +0200 [thread overview]
Message-ID: <20070803011448.GF14775@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708021801010.13312@schroedinger.engr.sgi.com>
On Thu, Aug 02, 2007 at 06:02:56PM -0700, Christoph Lameter wrote:
> On Fri, 3 Aug 2007, Nick Piggin wrote:
>
> > > Ok. So MPOL_BIND on a single node. We would have to save the current
> > > memory policy on the stack and then restore it later. Then you would need
> > > a special call anyways.
> >
> > Well the memory policy will already be set to MPOL_BIND at this point.
> > The slab allocator I think would just have to honour the node at the
> > object level.
>
> Who set the policy? The parent process may have its own memory policy. If
> you set that then the earlier policy is lost.
Yeah it only gets set if the parent is initially using a default policy
at this stage (and then is restored afterwards of course).
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-08-03 1:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 5:41 Nick Piggin
2007-07-31 8:01 ` Ingo Molnar
2007-08-01 0:21 ` Nick Piggin
2007-08-01 6:19 ` Ingo Molnar
2007-07-31 9:14 ` Andi Kleen
2007-07-31 23:40 ` Christoph Lameter
2007-08-01 8:39 ` Andi Kleen
2007-08-02 3:42 ` Nick Piggin
2007-08-02 19:58 ` Christoph Lameter
2007-08-03 0:26 ` Nick Piggin
2007-08-03 0:52 ` Christoph Lameter
2007-08-03 0:57 ` Nick Piggin
2007-08-03 1:02 ` Christoph Lameter
2007-08-03 1:14 ` Nick Piggin [this message]
2007-08-03 1:34 ` Christoph Lameter
2007-08-03 3:14 ` Nick Piggin
2007-08-03 5:47 ` Christoph Lameter
2007-08-01 0:23 ` Nick Piggin
2007-08-01 17:53 ` Martin Bligh
2007-08-01 18:32 ` Lee Schermerhorn
2007-08-01 22:52 ` Martin Bligh
2007-08-02 1:36 ` Nick Piggin
2007-08-02 18:33 ` Martin Bligh
2007-08-03 0:20 ` Nick Piggin
2007-08-03 20:10 ` Siddha, Suresh B
2007-08-06 1:20 ` Nick Piggin
2007-08-02 14:49 ` Lee Schermerhorn
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=20070803011448.GF14775@wotan.suse.de \
--to=npiggin@suse.de \
--cc=ak@suse.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox