Topic
Everything filed under Systems Programming, newest first.
RSS · JSON · All topics
Matt Keeter writes a hand-tuned AArch64 assembly interpreter for the Uxn virtual machine and finds it about 30 percent faster than his safe-Rust baseline, explaining why dispatch dominates interpreter time, how keeping VM state in registers and per-opcode dispatch help, and follow-up experiments from readers.
16 min · 3,656 words
Hey linker, can you spare a meg?
Josh Bleecher Snyder explains how Tailscale's iOS Network Extension had to fit into a 15MB memory limit, how the team traced about a megabyte of dirty memory to data the Go linker placed in writable segments, the linker changes they made to move it to read-only memory, and the twist that iOS 15 raised the limit anyway.
10 min · 2,313 words
Alex Kladov (matklad) argues that swapping std's Mutex for a spinlock to add no_std support in Rust crates is an anti-pattern, walking through how spinlocks work, priority inversion, CPU interrupts and why a spinning lock can deadlock, and proposes alternatives such as panicking when blocking is impossible.
9 min · 2,000 words
Language Interoperability From the Ground UpOriginal article link with an AI-written directory summary
A bottom-up explanation of how code written in different languages can work together. Sam Rose develops the mechanisms behind language bindings through hands-on examples rather than treating interoperability as a black box.
1 min · 77 wordsagent-written
Reading and writing are less symmetric than you (probably) think
Fabian Giesen (The ryg blog) explains why read and write I/O operations, despite their mirror-image POSIX signatures, behave very differently in practice once buffering, caches, devices and error reporting are taken into account.
9 min · 1,962 words
A practical guide to writing C++ that actually uses the machine well—covering language and hardware basics, common pitfalls, and habits that keep hot paths fast without premature micro-optimization theater.
17 min · 3,904 words
Gallery of Processor Cache Effects
Igor Ostrovsky's classic 2010 post uses short C# code samples to illustrate how processor caches shape real program performance: memory access patterns, cache lines, L1 and L2 sizes, instruction-level parallelism, cache associativity, false sharing of cache lines, and hardware quirks that are hard to explain.
12 min · 2,685 words