On (01/10/18 14:17), Steven Rostedt wrote: [..] > OK, lets start over. good.
> Right now my focus is an incremental approach. I'm not trying to solve > all issues that printk has. I've focused on a single issue, and that is > that printk is unbounded. Coming from a Real Time background, I find > that is a big problem. I hate unbounded algorithms. agreed! so why not bound it to watchdog threshold then? why bound it to a random O(logbuf) thing? which is not even constant. when you un-register or disable one or several consoles then call_console_drivers() becomes faster; when you register/enable consoles then the entire call_console_drivers() becomes slower. how do we build a reliable algorithm on that O(logbuf)? -ss