Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

[Peter Zijlstra]

On Wed, Jan 10, 2018 at 10:30:55AM -0800, Tejun Heo wrote:
> > Why not kill recursive OOM (msgs) ?
> 
> Sure, we can do that too, e.g. marking flushing thread and ignoring
> new messages from it, although that does come with its own downsides.

Typically we (scheduler) have removed printk()s (on boot) when BIGSMP
folks say it creates boot pain. Much of it is now behind the sched_debug
parameter, others are compressed.

I've also seen other people reduce printk()s.

In general reducing printk() is a good thing, its a low bandwidth
channel for critical stuff like OOPSen and the like.