• Peter Zijlstra's avatar
    lockstat: core infrastructure · f20786ff
    Peter Zijlstra authored
    Introduce the core lock statistics code.
    
    Lock statistics provides lock wait-time and hold-time (as well as the count
    of corresponding contention and acquisitions events). Also, the first few
    call-sites that encounter contention are tracked.
    
    Lock wait-time is the time spent waiting on the lock. This provides insight
    into the locking scheme, that is, a heavily contended lock is indicative of
    a too coarse locking scheme.
    
    Lock hold-time is the duration the lock was held, this provides a reference for
    the wait-time numbers, so they can be put into perspective.
    
      1)
        lock
      2)
        ... do stuff ..
        unlock
      3)
    
    The time between 1 and 2 is the wait-time. The time between 2 and 3 is the
    hold-time.
    
    The lockdep held-lock tracking code is reused, because it already collects locks
    into meaningful groups (classes), and because it is an existing infrastructure
    for lock instrumentation.
    
    Currently lockdep tracks lock acquisition with two hooks:
    
      lock()
        lock_acquire()
        _lo...
    f20786ff
Kconfig.debug 16.6 KB