On Fri, Aug 24, 2007 at 05:50:18PM -0700, Siddha, Suresh B wrote:
quoted text
> On Fri, Aug 24, 2007 at 03:26:54PM -0700, travis@sgi.com wrote:
> > Previous Intro:
> 
> Thanks for doing this.
> 
> > In x86_64 and i386 architectures most arrays that are sized
> > using NR_CPUS lay in local memory on node 0.  Not only will most
> > (99%?) of the systems not use all the slots in these arrays,
> > particularly when NR_CPUS is increased to accommodate future
> > very high cpu count systems, but a number of cache lines are
> > passed unnecessarily on the system bus when these arrays are
> > referenced by cpus on other nodes.
> 
> Can we move cpuinfo_x86 also to per cpu area? Though critical run

I worry how much impact that would be? boot_cpu_data is quite 
widely used. 

quoted text
> Wonder if this confusion is the reason for git commit f3fa8ebc

What git commit (full id) ? 

-Andi
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/