Why is printk() so complicated?

From LinuxReviews
Jump to navigationJump to search
Tux-000d-200.png

John Ogness have a great overview the Linux kernels printk() function, it's history, it's use and it's future at the Linux Plumbers Conference 2019. The video is 56 minutes long.


Video Copyright 2019 John Ogness / Linux Plumbers Conference 2019. Licensed under the Creative Commons Attribution (CC BY) license. Slides: Lpc2019 jogness printk.pdf

"The printk() function has a long history of issues and has undergone many iterations to improve performance and reliability. Yet it is still not an acceptable solution to reliably allow the kernel to send detailed information to the user. And these problems are even magnified when using a real-time system. So why is printk() so complicated and why are we having such a hard time finding a good solution?

This talk will briefly cover the history of printk() and why the recent major rework was necessary. It will go through the details of the rework and why we believe it solves many of the issues. And it will present the issues still not solved (such as fully synchronous console writing), why these issues are particularly complex and controversial, and review some of the proposed solutions for moving forward.

This talk may be of particular interest to developers with experience or interest in lockless ring buffers, memory barriers, and NMI-safe synchronization."

John Ogness (Linutronix GmbH)

Add your comment
LinuxReviews welcomes all comments. If you do not want to be anonymous, register or log in. It is free.