introduce sys_membarrier(): process-wide memory barrier (v9)
in [Kernel]
|
Prev: [git patches] boot fix for 2.6.33 for parisc
Next: [PATCH 02/11] KVM: SVM: Reset MMU on nested_svm_vmrun for NPT too
From: Darren Hart on 24 Feb 2010 12:40 Nick Piggin wrote: > When writing multiprocessor scalable software, threads should often be > avoided. They share so much state that it is easy to run into > scalability issues in the kernel. So yes it would be really nice to > have userspace RCU available in a process-shared mode. A bit off topic, but I'm interested in what you feel some of these scalability issues are. Is it mostly bouncing this shared context from one CPU to the next and the related cache effects, or is there something more you are referring to? -- Darren Hart IBM Linux Technology Center Real-Time Linux Team -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |