Documentation: locking: ww-mutex-design: drop duplicated word
Drop the doubled word "up". Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org Cc: Peter Zijlstra <peterz@infradead.org> Cc: Ingo Molnar <mingo@redhat.com> Cc: Will Deacon <will@kernel.org> Link: https://lore.kernel.org/r/20200703213649.30948-3-rdunlap@infradead.org Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
7d64394b51
commit
8b1a17c7c5
|
@ -49,7 +49,7 @@ However, the Wound-Wait algorithm is typically stated to generate fewer backoffs
|
||||||
compared to Wait-Die, but is, on the other hand, associated with more work than
|
compared to Wait-Die, but is, on the other hand, associated with more work than
|
||||||
Wait-Die when recovering from a backoff. Wound-Wait is also a preemptive
|
Wait-Die when recovering from a backoff. Wound-Wait is also a preemptive
|
||||||
algorithm in that transactions are wounded by other transactions, and that
|
algorithm in that transactions are wounded by other transactions, and that
|
||||||
requires a reliable way to pick up up the wounded condition and preempt the
|
requires a reliable way to pick up the wounded condition and preempt the
|
||||||
running transaction. Note that this is not the same as process preemption. A
|
running transaction. Note that this is not the same as process preemption. A
|
||||||
Wound-Wait transaction is considered preempted when it dies (returning
|
Wound-Wait transaction is considered preempted when it dies (returning
|
||||||
-EDEADLK) following a wound.
|
-EDEADLK) following a wound.
|
||||||
|
|
Loading…
Reference in New Issue