Fantastic Voyage III: Destination BEAM
summary
Examines concrete BEAM mechanics: how gen_server call uses monitors and a smuggled {self, mref} tuple, how Erlang :send is implemented through do_send → erl_message → queue_message as a linked‑list process queue with inner/middle Qs, and how atom-to-pid resolution uses a locked bucketing hash map via hash_put. Shows which cases avoid allocation (self-send), when delayed placement occurs, and where selective receive and mref matching guarantee correct replies.
AI-written summary · about
chapters (5)
related talks
48mGetting to Know the Erlang Virtual Machine, the BEAM
26mseL4 and BEAM: A match made in Erlang
38mDemos and Lightning Talks
27mFreestanding Erlang Porting BEAM close to the metal.
42mThe Soul of Erlang and Elixir
23mElixir GenServer: Understanding Elixir concurrency model
01h 07mInside memory management on the BEAM
45m12 years supporting Software Architecture teaching with BEAMs