On Wed, 21 Aug 2013 10:08:28 +0200 Jan Kara <j...@suse.cz> wrote: > These patches avoid softlockups when a CPU gets caught in console_unlock() for > a long time during heavy printing from other CPU. As is discussed in patch 3/4 > it isn't enough to just silence the watchdog because if CPU spends too long in > console_unlock() also RCU will complain, other CPUs can be blocked waiting for > printing CPU to process IPI, and even disk can be offlined because commands > couldn't be delivered to it for too long. > > This patch series solves the problem by stopping printing in console_unlock() > after 1000 characters and the printing is postponed to irq work. To avoid > hogging a single CPU (irq work gets processed on the same CPU where it was > queued so it doesn't really help to reduce the printing load on that CPU) we > introduce a new type of lazy irq work - IRQ_WORK_UNBOUND - which can be > processed by any CPU.
I still hate the patchset :( Remind us why we need this? Whose kernel is spewing so much logging and why? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
