On Tue, 22 Sep 2009, Tejun Heo wrote: > > +#ifdef CONFIG_SMP > + . = ALIGN(PERCPU_PAGE_SIZE); > + __cpu0_per_cpu = .; __per_cpu_start? > + . = . + PERCPU_PAGE_SIZE; /* cpu0 per-cpu space */ > +#endif This is a statically sized per cpu area that is used by __get_cpu_var() Data is access via a cpu specific memory mapping. How does this work when the area grows beyond PERCPU_PAGE_SIZE? As far as I can see: It seems that __get_cpu_var would then cause a memory fault? -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|