On Fri, May 25, 2007 at 01:19:44AM -0700, William Lee Irwin III wrote: >> I remember. It was far beyond "slightly async;" they would drift >> minutes apart during reasonable amounts of uptime, though it would take >> at least several days to drift so far (I don't recall how long it took).
On Fri, May 25, 2007 at 10:22:59AM +0200, Andi Kleen wrote: > sched_clock should handle that. On Fri, May 25, 2007 at 01:19:44AM -0700, William Lee Irwin III wrote: >> TSC synchronization is uniformly impossible on NUMA-Q. Bootlogs showing >> the results of the attempts are still extant. They shouldn't end up too >> far apart right after booting, but I don't have even ballpark estimates. >> I'd hazard a guess of a few seconds. On Fri, May 25, 2007 at 10:22:59AM +0200, Andi Kleen wrote: > You should mark_tsc_instable(), but not tsc disable. In a release or two > hopefully even that will be obsolete. I don't have any particular preference here. I'm just donating a memory dump. I have no intention of attempting to maintain NUMA-Q support code. -- wli - 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/
