Messages in this thread |  | | | Date | Mon, 6 Jun 2011 19:07:25 +0200 | | From | Ingo Molnar <> | | Subject | Re: [debug patch] printk: Add a printk killswitch to robustify NMI watchdog messages |
| |
* Arne Jansen <lists@die-jansens.de> wrote:
> > As long as it doesn't scramble the order of the messages, the > > delay imho doesn't matter even in very printk-heavy debugging > > sessions. > > And, as important, doesn't reduce the throughput of printk. Having > only 100 wakeups/s sounds like the throughput is limited to > 100xsizeof(ring buffer).
Nah.
I for example *always* kill klogd during such printk based debugging sessions, because it's *already* very easy to overflow its buffering abilities. Also, klogd often interferes with debugging.
So i make the log buffer big enough to contain enough debugging info.
So it's a non-issue IMHO. Linus, what do you think?
Thanks,
Ingo
|  |