| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071207221106.GH16824@localdomain> Date: Fri, 7 Dec 2007 16:11:06 -0600 From: Nathan Lynch <ntl@...ox.com> To: Balbir Singh <balbir@...ux.vnet.ibm.com> Cc: linuxppc-dev@...abs.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] Fake NUMA emulation for PowerPC 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? 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists