Re: [RFC] time: xtime_lock is held too long

[Ingo Molnar]

* Andi Kleen <andi@xxxxxxxxxxxxxx> wrote:

> > Then precise measurements have to be done on the source of cache misses, the 
> > total cost of the timer interrupt, etc.
> 
> What we did was profiling the remote node cache misses
> using raw offcore events, and the xtime code was high up.
> I cannot share exact numbers for various reasons, but it was
> an improvement on a hard to improve workload.

You could certainly share the profiling commands you typed, so that
others can reproduce and double check your results.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/