From: Christoph Lameter <clameter@xxxxxxx> Date: Thu, 1 Nov 2007 05:57:12 -0700 (PDT) > That is basically what IA64 is doing but it not usable because you would > have addresses that mean different things on different cpus. List head > for example require back pointers. If you put a listhead into such a per > cpu area then you may corrupt another cpus per cpu area. Indeed, but as I pointed out in another mail it actually works if you set some rules: 1) List insert and delete is only allowed on local CPU lists. 2) List traversal is allowed on remote CPU lists. I bet we could get all of the per-cpu users to abide by this rule if we wanted to. The remaining issue with accessing per-cpu areas at multiple virtual addresses is D-cache aliasing. - 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
