The article lives up to its title. Given its relatively short length, it does a good job explaining why printk() is so complicated. I loved this bit: " By 2.6.

The article lives up to its title. Given its relatively short length, it does a good job explaining why printk() is so complicated. I loved this bit: " By 2.6.26, printk() was causing large latency spikes; kernel developers dealt with this problem by ignoring printk() in the latency tracer, thus sweeping it under the rug."