linux-kernel - Re: [PATCH v2] Fix fake numa on ppc

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.00.0909021226160.10279@chino.kir.corp.google.com>
Date:	Wed, 2 Sep 2009 12:36:04 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Ankita Garg <ankita@...ibm.com>
cc:	LKML <linux-kernel@...r.kernel.org>, linuxppc-dev@...abs.org,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Balbir Singh <balbir@...ibm.com>,
	Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>
Subject: Re: [PATCH v2] Fix fake numa on ppc

On Wed, 2 Sep 2009, Ankita Garg wrote:

> Currently, the behavior of fake numa is not so on x86 as well? Below is
> a sample output from a single node x86 system booted with numa=fake=8:
> 
> # cat node0/cpulist
> 
> # cat node1/cpulist
> 
> ...
> # cat node6/cpulist
> 
> # cat node7/cpulist
> 0-7
> 
> Presently, just fixing the cpu association issue with ppc, as explained
> in my previous mail.
> 

Right, I'm proposing an alternate mapping scheme (which we've used for 
years) for both platforms such that a cpu is bound (and is set in 
cpumask_of_node()) to each fake node with which it has physical affinity.  
That is the only way for zonelist ordering in node order, task migration 
from offlined cpus, correct sched domains, etc.  I can propose a patchset 
for x86_64 to do exactly this if there aren't any objections and I hope 
you'll help do ppc.
--
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/