lkml.org 
[lkml]   [2010]   [Jan]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH] Add type of locks to lock trace events
    From
    Date
    On Fri, 2010-01-29 at 18:29 +0100, Frederic Weisbecker wrote:

    > > I still don't see the use for it, surely you're going to be familiar
    > > with the code if you're looking at lock statistics?

    > Comparing the avg/max time locks are acquired/waited between same
    > types of locks is interesting, but doing so between spinlocks and mutexes
    > is definetly pointless.

    Sure, never claimed otherwise, but:
    1) if you're looking at lock behaviour you should also look at the code
    otherwise you have no context to place the contention behaviour in.

    2) exactly because these hold/acquire times differ so much its hard to
    mistake mistake them for anything else.

    The concern I have is adding the storage (avoided by not doing it at
    init like you suggested) and the event size overhead. Jens' report
    confirms that we need to be very careful here, because lock sites are
    very high frequent.

    So again, _why_? If you're looking at these things its easy (and I'd say
    rather crucial) to look up the code.

    There simply is no point in looking at these stats if you're not also
    going to look at the code. If you're looking at them in a quick
    diagnostic way, then the difference against the baseline is important.



    \
     
     \ /
      Last update: 2010-01-29 18:43    [W:0.028 / U:31.060 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site