Concurrency in Go: From Hardware to Code ☠️
summary
Explains what mutexes and atomic operations actually are and how they work under the hood, relating hardware-level behavior to Go concurrency primitives. Covers when and why mutexes and atomics are needed in Go, and clarifies assumptions about atomicity of variable writes and potential pitfalls.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:11Concurrency pitfalls
- 4:13CPU and cache basics
- 7:47Memory barriers role
- 10:15Atomic ops in Go
- 12:43Atomic ops on architectures
- 18:01Spinlocks usage
- 19:46Go mutexes internals
- 29:03High-level abstractions limits
- 31:52Q&A
related talks
44mConcurrency in Go: from hardware to code ☠️
26mConcurrency primitives of Golang - how to use and how not to
24mMastering Concurrency in Go: From Patterns to Production
01h 00mConcurrency in C++20: A Deep Dive
39mLet's talk concurrency
01h 14m“C++ atomics, from basic to advanced. What do they really do?”
16mIn the Land of Gophers (from Age 3)
41mEverything You Don’t Want to Know About Concurrency on the JVM