Re: [PATCH v2] Fix fake numa on ppc

2009-09-02 Thread David Rientjes
On Thu, 3 Sep 2009, Balbir Singh wrote: > > 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 zoneli

Re: [PATCH v2] Fix fake numa on ppc

2009-09-02 Thread Balbir Singh
On Thu, Sep 3, 2009 at 1:06 AM, David Rientjes wrote: > 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 >

Re: [PATCH v2] Fix fake numa on ppc

2009-09-02 Thread David Rientjes
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

Re: [PATCH v2] Fix fake numa on ppc

2009-09-02 Thread Ankita Garg
Hi David, On Tue, Sep 01, 2009 at 11:37:05PM -0700, David Rientjes wrote: > On Wed, 2 Sep 2009, Ankita Garg wrote: > > > Hi, > > > > Below is a patch to fix a couple of issues with fake numa node creation > > on ppc: > > > > 1) Presently, fake nodes could be created such that real numa node > >

Re: [PATCH v2] Fix fake numa on ppc

2009-09-01 Thread David Rientjes
On Wed, 2 Sep 2009, Ankita Garg wrote: > Hi, > > Below is a patch to fix a couple of issues with fake numa node creation > on ppc: > > 1) Presently, fake nodes could be created such that real numa node > boundaries are not respected. So a node could have lmbs that belong to > different real node

[PATCH v2] Fix fake numa on ppc

2009-09-01 Thread Ankita Garg
Hi, Below is a patch to fix a couple of issues with fake numa node creation on ppc: 1) Presently, fake nodes could be created such that real numa node boundaries are not respected. So a node could have lmbs that belong to different real nodes. 2) The cpu association is broken. On a JS22 blade fo