On Friday 27 of August 2010 22:29:41 Luck, Tony wrote: > > If this is a memory ordering problem (and that seems quite plausible) > > then a liberal sprinkling of "ia64_mf()" calls throughout the spinlock > > routines would probably make it go away. > > I think I take this back ... if it were a memory ordering problem, then > it could show up any time - not just at wrap-around. One more idea. The wrap-around case is the only one when the high word is modified. This is in fact the only case when the fetchadd.acq competes with the st2.rel about the actual contents of that location. I don't know if it matters... Petr Tesarik -- 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
|