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

From: Eric Dumazet
Date: Fri May 06 2011 - 13:09:50 EST


Le vendredi 06 mai 2011 Ã 18:59 +0200, Andi Kleen a Ãcrit :
> On Fri, May 06, 2011 at 12:18:27PM +0200, Thomas Gleixner wrote:

> If that code path shows up in profiling. Only the timer interrupt
> did so far.
>
> > That's the completely wrong aproach, really. If stuff takes too long,
> > then we need to tackle it at the root of the problem and not solve it
> > by sprinkling magic prefetches all over the place.
>
> If you have a better way to make it faster please share it.
>

Unless I am very mistaken, it cannot explain my original report of up to
24.000 instructions waiting in ktime_get()

BTW, how many consecutive prefetch() a cpu can 'store/execute' before
throwing away hints ?



--
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/