|
|
Subscribe / Log in / New account

Why printk() is so complicated (and how to fix it)

Why printk() is so complicated (and how to fix it)

Posted Oct 4, 2019 19:55 UTC (Fri) by valarauca (guest, #109490)
In reply to: Why printk() is so complicated (and how to fix it) by shalem
Parent article: Why printk() is so complicated (and how to fix it)

Situation: There are 5 different competing ring buffers

> Maybe we need one ring (buffer) to rule them all?

Situation: There are 6 different competing ring buffers

credit: https://xkcd.com/927/


to post comments

Why printk() is so complicated (and how to fix it)

Posted Oct 7, 2019 13:10 UTC (Mon) by bene42 (subscriber, #32623) [Link]

I am not aware that there are more competing multiple reader/multiple writer ringbuffer implementations out there.
A link would be very helpful. Maybe there is a simpler solution, since the new one is quite complex and hard to understand...


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds