Fine, let's call evlog "an enhanced printk" and discuss the specific technical
details of the proposition.
> Evlog side-by-side with printk adds significat bloat.
Whenever you change/enhance such things you may need coexistance for a while.
However this is configurable, and to a certain extent temporary, bloat.
> > - Structured data events for which it is easier to apply filtering, querying,
> > analysis and detection tools.
>
> this is a post processing problem.
...
> What I hear you asking for, is to make it more of
> the kernels responsibilty easing the problem of analysing the out put,
> as opposed to making that the responsibilty of user space
> postprocessing.
Actually this is pushing the formatting out of the kernel, is more efficient,
and it leaves more flexibility to the logging daemon!
-
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/