lkml.org 
[lkml]   [2002]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Event logging vs enhancing printk
>   If you want buffering you can add it on a case-by-case basis, but in
> general I don't believe you do want a delay, because the output might be
> lost on a dying system. Prink works like output to stderr, character
> buffered. I would think a change to anything this fundimental would be a
> Linus decision, but I think it's correct as is.

OK, now try to read the panic output when two cpus panic at once ;-)
Been there, sworn vehemently at that ...

There's no point in logging messages if you can't read them afterwards.
I think 99.99% of such cases would not involve printk printing half
a buffered line, then dying, though I admit it's technically possible.

Of course, we could just do this buffering for the event logging half
of the subsystem if people really object. Personally, I think it's a
win to fix printk whilst we're at it, but a half-fix is always an
option.

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.071 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site