On Fri, 30 May 2008, Peter Zijlstra wrote: > Yes, I get that, but for instance kmem_cache_cpu usage would require > horrible long preempt off sections, hence we add a lock and manage > consistency using that lock instead of strict per-cpu and preempt > disable. Really? Where is that horrible long preempt off section? I thought they were all short and we use semaphores when looping over all slabs. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html