vault backup: 2025-03-24 08:34:22

This commit is contained in:
Marco Realacci 2025-03-24 08:34:23 +01:00
parent a8808b5953
commit 151e0612f0
2 changed files with 13 additions and 5 deletions

View file

@ -6,7 +6,7 @@
{
"id": "4c1f5b7a6abb1339",
"type": "tabs",
"dimension": 41.54727793696275,
"dimension": 41.54727793696274,
"children": [
{
"id": "105f7a61963f10e7",
@ -38,7 +38,7 @@
"file": "Concurrent Systems/slides/class 6.pdf",
"page": 8,
"left": -23,
"top": 483,
"top": 568,
"zoom": 0.6805225653206651
},
"icon": "lucide-file-text",
@ -218,10 +218,10 @@
"companion:Toggle completion": false
}
},
"active": "105f7a61963f10e7",
"active": "6c846cff8fe1d071",
"lastOpenFiles": [
"Concurrent Systems/slides/class 6.pdf",
"Concurrent Systems/notes/6a - Alternatives to Atomicity.md",
"Concurrent Systems/slides/class 6.pdf",
"Pasted image 20250324082545.png",
"Pasted image 20250324082534.png",
"Concurrent Systems/notes/6 - Atomicity.md",

View file

@ -5,4 +5,12 @@ Let us define $op ->_{proc} op'$ to hold whenever there exists a process p that
![[Pasted image 20250324082545.png]]
The problem with sequential consistency is that it
>[!warning]
>The problem with sequential consistency is that it is NOT compositional.
Consider for example the following two processes:
```
p1: Q.enq(a); Q'.enq(b'); Q'deq()->b'
p2: Q'.enq(a'); Q.enq(b); Q.deq()->b
```