From aa6d7e576be2b29c393a1d4f15404a4e34c6e028 Mon Sep 17 00:00:00 2001 From: Marco Realacci Date: Fri, 21 Mar 2025 19:05:08 +0100 Subject: [PATCH] vault backup: 2025-03-21 19:05:08 --- Concurrent Systems/notes/4b - Monitors.md | 1 - 1 file changed, 1 deletion(-) diff --git a/Concurrent Systems/notes/4b - Monitors.md b/Concurrent Systems/notes/4b - Monitors.md index bd145ed..4a96ae4 100644 --- a/Concurrent Systems/notes/4b - Monitors.md +++ b/Concurrent Systems/notes/4b - Monitors.md @@ -33,7 +33,6 @@ Of course, `signal()` will have no effect on the last process who calls it. - A semaphore MUTEX init at 1 (to guarantee mutex in the monitor) - For every condition C, a semaphore SEMC init at 0 and an integer $N_{C}$ init at 0 (to store and count the number of suspended processes on the given condition) - A semaphore PRIO init at 0 and an integer $N_{PR}$ init at 0 (to store and count the number of processes that have performed a signal, and so have priority to re-enter the monitor) - >[!note]Operations >Every monitor operation starts with `MUTEX.down()` and ends with `if NPR > 0 then PRIO.up() else MUTEX.up()`