Lines Matching refs:Wait

2 Wound/Wait Deadlock-Proof Mutex Design
37 and the deadlock handling approach is called Wait-Die. The name is based on
41 and dies. Hence Wait-Die.
42 There is also another algorithm called Wound-Wait:
46 transaction. Hence Wound-Wait.
48 However, the Wound-Wait algorithm is typically stated to generate fewer backoffs
49 compared to Wait-Die, but is, on the other hand, associated with more work than
50 Wait-Die when recovering from a backoff. Wound-Wait is also a preemptive
54 Wound-Wait transaction is considered preempted when it dies (returning
72 class also specifies what algorithm to use, Wound-Wait or Wait-Die.
113 The algorithm (Wait-Die vs Wound-Wait) is chosen by using either
114 DEFINE_WW_CLASS() (Wound-Wait) or DEFINE_WD_CLASS() (Wait-Die)
115 As a rough rule of thumb, use Wound-Wait iff you
346   (2) For Wait-Die, among waiters with contexts, only the first one can have
350   The Wound-Wait preemption is implemented with a lazy-preemption scheme: