lkml.org 
[lkml]   [2011]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] time: xtime_lock is held too long

* Andi Kleen <andi@firstfloor.org> 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


\
 
 \ /
  Last update: 2011-05-07 10:23    [W:0.084 / U:1.932 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site