On Mon, 27 Aug 2007, Mathieu Desnoyers wrote: > Hrm, I just want to certify one thing: A lot of code paths seems to go > to the slow path without requiring cmpxchg_local to execute at all. So > is the slow path more likely to be triggered by the (!object), > (!node_match) tests or by these same tests done in the redo after the > initial cmpxchg_local ?
The slow path is more likely to be triggered by settings in the per cpu structure. The cmpxchg failure is comparatively rare. So the worst case is getting worse but the average use of interrupt enable/disable may not change much. Need to have some measurements to confirm that. I can try to run the emulation on IA64 and see what the result will be. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
