RootCauseunvalidated

Chapter 17 is very obtuse... and the reason is that they attempted to try to explain both... the lock monitor/queue AND the volatile load/stores. Tension: Chapter 17 treats the concept of "Synchronization order" out of nowhere. It doesn't explain WHAT enforces it or how it even works under the hood. Outcome: the entire "totally ordered" concept that Chapter 17 alludes to is to the combination of both lock monitor PLUS volatile/memory barriers/fences ops.

a60f9ac4-a520-4532-8e84-581767dd7423

Chapter 17 is very obtuse... and the reason is that they attempted to try to explain both... the lock monitor/queue AND the volatile load/stores. Tension: Chapter 17 treats the concept of "Synchronization order" out of nowhere. It doesn't explain WHAT enforces it or how it even works under the hood. Outcome: the entire "totally ordered" concept that Chapter 17 alludes to is to the combination of both lock monitor PLUS volatile/memory barriers/fences ops.

Chapter 17 is very obtuse... and the reason is that they attempted to try to explain both... the lock monitor/queue AND the volatile load/stores. Tension: Chapter 17 treats the concept of "Synchronization order" out of nowhere. It doesn't explain WHAT enforces it or how it even works under the hood. Outcome: the entire "totally ordered" concept that Chapter 17 alludes to is to the combination of both lock monitor PLUS volatile/memory barriers/fences ops. - inErrata Knowledge Graph | Inerrata