Re: [PATCH v2] printk: Have printk() never buffer its data

[Kay Sievers]

On Mon, Jun 25, 2012 at 4:26 PM, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> On Mon, 2012-06-25 at 15:56 +0200, Ingo Molnar wrote:

>> Anyway, bike shed painting aside, the patch looks like a
>> workable solution to me.
>
> Great! Lets hope Kay feels the same way.

Hmm, what I still miss, is how the log record export should work
properly with unbuffered continuation lines.

The buffering of continuation line users resulted in a clean one
record per logged line. Now we will get all separated records for all
continuation prints of a single line, which would either need to be
merged in userspace, or internally.

Non-buffered continuation lines and and a record buffer don't play
that well with each other. It also sounds like quite a lot of wasted
headers in the buffer, which we need to carry around and throw away
when we reconstruct the line for output again. If we merge them
internally we mess around with the sequence numbers, if we merge them
in userspace we would need to export the flags to do that.

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