linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fake NUMA emulation for PowerPC
Date: Sat, 08 Dec 2007 03:56:35 +0530	[thread overview]
Message-ID: <4759C89B.9000709@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071207221106.GH16824@localdomain>

Nathan Lynch wrote:
> Hi Balbir-
> 
> Balbir Singh wrote:
>>
>> Here's a dumb simple implementation of fake NUMA nodes for PowerPC. Fake
>> NUMA nodes can be specified using the following command line option
>>
>> numa=fake=<node range>
>>
>> node range is of the format <range1>,<range2>,...<rangeN>
>>
>> Each of the rangeX parameters is passed using memparse(). I find the patch
>> useful for fake NUMA emulation on my simple PowerPC machine. I've tested it
>> on a non-numa box with the following arguments
>>
>> numa=fake=1G
>> numa=fake=1G,2G
>> name=fake=1G,512M,2G
>> numa=fake=1500M,2800M mem=3500M
>> numa=fake=1G mem=512M
>> numa=fake=1G mem=1G
> 
> So this doesn't appear to allow one to assign cpus to fake nodes?  Do
> all cpus just get assigned to node 0 with numa=fake?
> 

Yes, they all appear on node 0. We could have tweaks to distribute CPU's
as well.

> A different approach that occurs to me is to use kexec with a doctored
> device tree (i.e. with the ibm,associativity properties modified to
> reflect your desired topology).  Perhaps a little bit obscure, but it
> seems more flexible.
> 

That would be interesting, but it always means that we need to run
kexec, which might involve two boots.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

  parent reply	other threads:[~2007-12-07 22:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 21:14 [PATCH] Fake NUMA emulation for PowerPC Balbir Singh
2007-12-07 21:28 ` Olof Johansson
2007-12-07 21:35   ` Balbir Singh
2007-12-07 21:55     ` Kumar Gala
2007-12-07 22:12       ` Balbir Singh
2007-12-07 22:15         ` Kumar Gala
2007-12-07 22:18           ` Balbir Singh
2007-12-07 23:10         ` David Rientjes
2007-12-08  4:22           ` Balbir Singh
2007-12-09 13:16             ` Pavel Machek
2007-12-09 13:20               ` Balbir Singh
2007-12-07 23:06   ` David Rientjes
2007-12-07 21:30 ` Geert Uytterhoeven
2007-12-07 21:35   ` Balbir Singh
2007-12-07 21:43     ` Balbir Singh
2007-12-07 21:58       ` Arnd Bergmann
2007-12-07 22:03         ` Balbir Singh
2007-12-07 22:01 ` Arnd Bergmann
2007-12-07 22:22   ` Balbir Singh
     [not found] ` <20071207221106.GH16824@localdomain>
2007-12-07 22:26   ` Balbir Singh [this message]
2007-12-07 23:11     ` David Rientjes
2007-12-08  4:32       ` Balbir Singh
2007-12-08  4:45         ` David Rientjes

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=4759C89B.9000709@linux.vnet.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ntl@pobox.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;
as well as URLs for NNTP newsgroup(s).