On Thu, 24 Sep 2009, Tejun Heo wrote: > > How does the new percpu allocator support this? Does it use different > > methods of access for static and dynamic percpu access? > > That's only when __ia64_per_cpu_var() macro is used in arch code which > always references static perpcu variable in the kernel image which > falls inside PERCPU_PAGE_SIZE. For everything else, __my_cpu_offset > is defined as __ia64_per_cpu_var(local_per_cpu_offset) and regular > pointer offsetting is used. So this means that address arithmetic needs to be performed for each percpu access. The virtual mapping would allow the calculation of the address at link time. Calculation means that a single atomic instruction for percpu access wont be possible for ia64. I can toss my ia64 percpu optimization patches. No point anymore. Tony: We could then also drop the virtual per cpu mapping. Its only useful for arch specific code and an alternate method of reference exists. -- 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
![]() |