From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
apw@shadowen.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated
Date: Tue, 5 Dec 2006 10:26:54 -0800 [thread overview]
Message-ID: <20061205102654.19165150.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612050803000.11213@schroedinger.engr.sgi.com>
On Tue, 5 Dec 2006 08:05:16 -0800 (PST)
Christoph Lameter <clameter@sgi.com> wrote:
> On Tue, 5 Dec 2006, Mel Gorman wrote:
>
> > That is one possibility. There are people working on fake nodes for containers
> > at the moment. If that pans out, the infrastructure would be available to
> > create one node per DIMM.
>
> Right that is a hack in use for one project.
Other projects can use it too. It has the distinct advantage that it works
with today's VM.
> We would be adding huge
> amounts of VM overhead if we do a node per DIMM.
No we wouldn't.
> So a desktop system with two dimms is to be treated like a NUMA
> system?
Could do that. Or make them separate zones.
> Or how else do we deal with the multitude of load balancing
> situations that the additional nodes will generate?
No such problems are known.
--
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:[~2006-12-05 18:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 17:07 Mel Gorman
2006-12-01 1:31 ` Andrew Morton
2006-12-01 9:54 ` Mel Gorman
2006-12-01 19:01 ` Andrew Morton
2006-12-04 14:07 ` Mel Gorman
2006-12-04 19:30 ` Andrew Morton
2006-12-04 19:41 ` Christoph Lameter
2006-12-04 20:06 ` Andrew Morton
2006-12-04 20:17 ` Christoph Lameter
2006-12-04 21:19 ` Andrew Morton
2006-12-04 21:43 ` Christoph Lameter
2006-12-04 22:22 ` Andrew Morton
2006-12-05 16:00 ` Christoph Lameter
2006-12-05 19:25 ` Andrew Morton
2006-12-05 20:01 ` Christoph Lameter
2006-12-05 21:47 ` Mel Gorman
2006-12-05 23:33 ` Christoph Lameter
2006-12-06 9:31 ` Mel Gorman
2006-12-06 17:31 ` Christoph Lameter
2006-12-08 1:21 ` Jeremy Fitzhardinge
2006-12-08 2:20 ` Christoph Lameter
2006-12-08 6:11 ` Jeremy Fitzhardinge
2006-12-05 18:10 ` Mel Gorman
2006-12-04 20:34 ` Mel Gorman
2006-12-04 22:34 ` Andrew Morton
2006-12-04 23:45 ` Mel Gorman
2006-12-05 1:16 ` KAMEZAWA Hiroyuki
2006-12-05 10:03 ` Mel Gorman
2006-12-05 16:05 ` Christoph Lameter
2006-12-05 18:26 ` Andrew Morton [this message]
2006-12-05 19:59 ` Christoph Lameter
2006-12-05 16:14 ` Christoph Lameter
2006-12-05 17:17 ` Mel Gorman
2006-12-05 19:54 ` Christoph Lameter
2006-12-05 15:52 ` Andy Whitcroft
2006-12-05 15:48 ` Andy Whitcroft
2006-12-04 20:37 ` Peter Zijlstra
2006-12-06 14:18 ` Andy Whitcroft
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=20061205102654.19165150.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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