diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json index 3035418..643eb4c 100644 --- a/.obsidian/workspace.json +++ b/.obsidian/workspace.json @@ -211,13 +211,13 @@ "active": "dd6c003f9d17b0e9", "lastOpenFiles": [ "Concurrent Systems/notes/3a - Hardware primitives & Lamport Bakery algorithm.md", + "Concurrent Systems/notes/3b - Aravind's algorithm and improvements.md", + "Concurrent Systems/notes/1 - CS Basics.md", "Concurrent Systems/notes/2b - Round Robin algorithm.md", "Concurrent Systems/notes/2 - Fast mutex by Lamport.md", - "Concurrent Systems/notes/3b - Aravind's algorithm and improvements.md", "Concurrent Systems/slides/class 3.pdf", "Pasted image 20250310172134.png", "Pasted image 20250310103703.png", - "Concurrent Systems/notes/1 - CS Basics.md", "Concurrent Systems/notes/1 - CS Basics2.md", "Concurrent Systems/notes/1b - Peterson algorithm.md", "HCIW/slides/Interface and Interaction for IoT.pdf", diff --git a/Concurrent Systems/notes/3a - Hardware primitives & Lamport Bakery algorithm.md b/Concurrent Systems/notes/3a - Hardware primitives & Lamport Bakery algorithm.md index 1876ec0..155d6b4 100644 --- a/Concurrent Systems/notes/3a - Hardware primitives & Lamport Bakery algorithm.md +++ b/Concurrent Systems/notes/3a - Hardware primitives & Lamport Bakery algorithm.md @@ -105,7 +105,7 @@ unlock() := return ``` ->[!note] a>It is bounded bypass with bound n-1> +>[!note] It is bounded bypass with bound n-1> ### Safe registers Atomic R/W and specialized HW primitives provide some form of atomicity. But is it possible to enforce MUTEX without atomicity?