Re: [PATCH] printk: robustify printk

[Andi Kleen <andi@firstfloor.org>]

> That's a rather misleading argument, because klogd as it stands today is 
> already lossy: you can overflow it with enough printk data. (It's rather 

That's true, but with at least the timer tick version it would become much 
worse I think, because there would be a rather low upper limit on
the maximum frequency of klogd wakeups.

Not fully sure about the RCU version, i guess it would depend on 
how many CPUs you have (but that one had the problem of
"cannot put printks into RCU anymore")

BTW if you only care about the console you can always use early_printk()
at least for serial/vga/usb debug on x86 -- it will never lose anything (at 
least as long as you can read the output fast enough) and also
works in nearly any context. But of course since it also doesn't
log anything to klogd it's probably not a good idea outside debugging.

-Andi