> This cache-line bouncing global clock is a best-effort to provide > correct event order in the trace on architectures with unsync tsc. It's > actually better than a global tracing buffer because it limits the > number of cache line transfers required to one per event. 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 applications that are overly fond of timestamping internal events using gettimeofday() end up spending significant time doing so on large systems ... even with only a few thousands of calls per second). -Tony -- 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
