Messages in this thread | | | From | Linus Torvalds <> | Date | Mon, 25 Jun 2012 18:40:47 -0700 | Subject | Re: [PATCH v3] printk: Have printk() never buffer its data |
| |
On Mon, Jun 25, 2012 at 5:56 PM, Kay Sievers <kay@vrfy.org> wrote: > > Buffering has nice effects though: > It makes continuation lines appear as one record in the buffer, not as > n individual prints with n headers.
As I already mentioned, buffering for *logging* is different from buffering for *printing*.
I think it might be a great idea to buffer for logging in order to generate one individual buffer record there.
But it needs to be printed as it is generated.
The printing and the recording really should be thought of as separate issues. You already record things that aren't printed, so they already aren't 1:1 relationships.
Linus
| |