Lines Matching refs:lock
14 Because things like lock contention can severely impact performance.
19 Lockdep already has hooks in the lock functions and maps lock instances to
20 lock classes. We build on that (see Documentation/locking/lockdep-design.rst).
21 The graph below shows the relation between the lock functions and the various
26 lock _____
44 lock, unlock - the regular lock functions
51 - number of lock contention that involved x-cpu data
53 - number of lock acquisitions that had to wait
56 - shortest (non-0) time we ever had to wait for a lock
58 - longest time we ever had to wait for a lock
60 - total time we spend waiting on this lock
62 - average time spent waiting on this lock
64 - number of lock acquisitions that involved x-cpu data
66 - number of times we took the lock
69 - shortest (non-0) time we ever held the lock
71 - longest time we ever held the lock
73 - total time this lock was held
75 - average time this lock was held
77 These numbers are gathered per lock class, per read/write state (when
81 that had to wait on lock acquisition.
99 Look at the current lock statistics::
139 This excerpt shows the first two lock class statistics. Line 01 shows the
146 which tries to get the lock) and lines 14-17 show the first 4 recorded
147 contended points (the lock holder). It is possible that the max
150 The first lock (05-18) is a read/write lock, and shows two lines above the
161 …34 &rq->lock: 13128 13128 0.43 190.…
163 …36 &rq->lock 645 [<ffffffff8103bfc4>] task_rq_lock…
164 …37 &rq->lock 297 [<ffffffff8104ba65>] try_to_wake_…
165 …38 &rq->lock 360 [<ffffffff8103c4c5>] select_task_…
166 …39 &rq->lock 428 [<ffffffff81045f98>] scheduler_ti…
168 …41 &rq->lock 77 [<ffffffff8103bfc4>] task_rq_lock…
169 …42 &rq->lock 174 [<ffffffff8104ba65>] try_to_wake_…
170 …43 &rq->lock 4715 [<ffffffff8103ed4b>] double_rq_lo…
171 …44 &rq->lock 893 [<ffffffff81340524>] schedule+0x1…
175 …48 &rq->lock/1: 1526 11488 0.33 388.…
177 …50 &rq->lock/1 11526 [<ffffffff8103ed58>] double_rq_lo…
179 …52 &rq->lock/1 5645 [<ffffffff8103ed4b>] double_rq_lo…
180 …53 &rq->lock/1 1224 [<ffffffff81340524>] schedule+0x1…
181 …54 &rq->lock/1 4336 [<ffffffff8103ed58>] double_rq_lo…
182 …55 &rq->lock/1 181 [<ffffffff8104ba65>] try_to_wake_…
184 Line 48 shows statistics for the second subclass (/1) of &rq->lock class
186 double_rq_lock actually acquires a nested lock of two spinlocks.
194 …&rq->lock: 135014 136909 0.18 606.09 842160.68 6.1…
199 …&(&dentry->d_lockref.lock)->rlock: 39791 40179 0.15 1302.08 …