From: Andi Kleen <ak@suse.de>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm <linux-mm@kvack.org>,
Christoph Lameter <clameter@sgi.com>,
Nishanth Aravamudan <nacc@us.ibm.com>,
kxr@sgi.com, akpm@linux-foundation.org,
Eric Whitney <eric.whitney@hp.com>
Subject: Re: [PATCH/RFC] Allow selected nodes to be excluded from MPOL_INTERLEAVE masks
Date: Wed, 1 Aug 2007 12:33:01 +0200 [thread overview]
Message-ID: <200708011233.02103.ak@suse.de> (raw)
In-Reply-To: <20070801101651.GA9113@linux-sh.org>
On Wednesday 01 August 2007 12:16:51 Paul Mundt wrote:
> Well, it's not so much the interleave that's the problem so much as
> _when_ we interleave. The problem with the interleave node mask at system
> init is that the kernel attempts to spread out data structures across
> these nodes, which results in us being completely out of memory by the
> time we get to userspace. After we've booted, supporting MPOL_INTERLEAVE
> is not so much of a problem, applications just have to be careful with
> their allocations.
I assume you got a mostly flat latency machine with a few additional
small nodes for special purposes, right?
Would the problem be solved if you just had a per arch CONFIG
to disable interleaving at boot? That would be really simple.
-Andi (who is a bit sceptical of more and more boot options)
--
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-01 10:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 20:07 Lee Schermerhorn
2007-07-28 6:19 ` KAMEZAWA Hiroyuki
2007-07-30 16:13 ` Lee Schermerhorn
2007-07-30 18:29 ` Christoph Lameter
2007-07-30 20:32 ` Lee Schermerhorn
2007-07-30 21:57 ` Christoph Lameter
2007-08-01 10:16 ` Paul Mundt
2007-08-01 10:33 ` Andi Kleen [this message]
2007-08-01 11:01 ` Paul Mundt
2007-08-01 11:07 ` Andi Kleen
2007-08-01 11:21 ` Paul Mundt
2007-08-01 13:54 ` Lee Schermerhorn
2007-08-02 17:38 ` Mark Gross
2007-08-02 18:46 ` Lee Schermerhorn
2007-08-06 16:42 ` Mark Gross
2007-08-01 13:39 ` Lee Schermerhorn
2007-08-03 7:53 ` Paul Mundt
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=200708011233.02103.ak@suse.de \
--to=ak@suse.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=eric.whitney@hp.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kxr@sgi.com \
--cc=lethal@linux-sh.org \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox