Luck, Tony wrote: > Even one line bouncing between cpus can be a performamce disaster. > You'll probably hit a serious wall somewhere between 8 and 16 > cpus (ia64 has code that looks a lot like this in the gettimeofday() > path because it does not synchronize cpu cycle counters ... some The code exist by necessity because some systems do not have synchronized ITCs and one would not have time go backward. The cmpxchg there is usually switched off. Its horrible in terms of scaling to large numbers of processor and also horrible in terms of clock accuracy. -- 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
