From 447835c45c15c13b78f63c6775423a0e31235b1f Mon Sep 17 00:00:00 2001 From: Marco Realacci Date: Tue, 25 Mar 2025 15:17:04 +0100 Subject: [PATCH] vault backup: 2025-03-25 15:17:04 --- Concurrent Systems/notes/8 - Enhancing Liveness Properties.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md b/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md index 02a95c5..3d54c65 100644 --- a/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md +++ b/Concurrent Systems/notes/8 - Enhancing Liveness Properties.md @@ -6,7 +6,8 @@ Can we take the most basic protocol that satisfies the most basic liveness prope **Enriched implementation:** when a process realizes that there is contention, it invokes need_help; when it completes its current operation, it invokes stop_help. -**Why is it different from lock/unlock?** Because this allows failures, and they can also happen in the contention-free period. +>[!question] Why is it different from lock/unlock? +>Because this allows failures, and they can also happen in the contention-free period. **PROBLEM:** to distinguish a failure from a long delay, we need objects called ***failure detectors***, that provide processes information on the failed processes of the system. According to the type/quality of the info, several F.D.s can be defined.