Searched refs:deadlocks (Results 1 – 21 of 21) sorted by relevance
76 unsigned long deadlocks; member314 __get_cpu_var(ptcstats).deadlocks++; in sn2_global_tlb_purge()337 __get_cpu_var(ptcstats).deadlocks++; in sn2_ptc_deadlock_recovery()497 stat->deadlocks, in sn2_ptc_seq_show()
34 file with flock(). With pre 1.3.96 kernels this could result in deadlocks that,
210 in all cases except some malicious deadlocks
168 This introduces lots of scope for deadlocks with transactions that are already527 The problem with this is that it can lead to deadlocks as we may need to commit546 up front. This avoids deadlocks and removes a blocking point from the
255 This may also be done to avoid internal deadlocks, but rarely.
630 various race conditions and deadlocks.
82 to lock recursion deadlocks.89 because this could lead to lock inversion deadlocks. (The validator186 example, complex deadlocks that would normally need more than 3 CPUs and
104 * - detects multi-task circular deadlocks and prints out all affected
113 play with the spinlock is that you can get deadlocks:
51 including proneness to deadlocks around the single execution context.147 pressure. Else it is possible that the thread-pool deadlocks waiting
115 deadlocks.
3316 device. In order to avoid deadlocks, it is recommended that the locks
8 deadlocks and the like.
11 __GFP_IO allocation requests are made to prevent file system deadlocks.
73 deadlocks when using in a nested fashion, and so it is not recommended for
53 avoid deadlocks with garbage collection -- the VFS will lock the i_sem
107 deadlocks. The late revelation of these problems - and refusal to
486 deadlocks (lockups) to be detected and reported automatically.507 deadlocks are also debuggable.549 related deadlocks before they actually occur.
304 not to introduce deadlocks.
546 to better handle low memory problems (and potential deadlocks).
630 deadlocks, e.g. avoid trying to allocate more memory from the pool while