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: Thu, 2 Aug 2007 05:42:01 +0200 [thread overview]
Message-ID: <20070802034201.GA32631@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0707311639450.31337@schroedinger.engr.sgi.com>
On Tue, Jul 31, 2007 at 04:40:18PM -0700, Christoph Lameter wrote:
> On Tue, 31 Jul 2007, Andi Kleen wrote:
>
> > On Tuesday 31 July 2007 07:41, Nick Piggin wrote:
> >
> > > I haven't given this idea testing yet, but I just wanted to get some
> > > opinions on it first. NUMA placement still isn't ideal (eg. tasks with
> > > a memory policy will not do any placement, and process migrations of
> > > course will leave the memory behind...), but it does give a bit more
> > > chance for the memory controllers and interconnects to get evenly
> > > loaded.
> >
> > I didn't think slab honored mempolicies by default?
> > At least you seem to need to set special process flags.
>
> It does in the sense that slabs are allocated following policies. If you
> want to place individual objects then you need to use kmalloc_node().
Is there no way to place objects via policy? At least kernel stack and page
tables on x86-64 should be covered by page allocator policy, so the patch
will still be useful.
--
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-02 3:42 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 [this message]
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
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=20070802034201.GA32631@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