From: Michel Dagenais <michel.dagenais@polymtl.ca>
To: Brian Beattie <alchemy@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Martin@m3.polymtl.ca,
"Martin.Bligh@us.ibm.com" <J.Bligh@m3.polymtl.ca>,
Tony.P.Lee@nokia.com, kessler@us.ibm.com,
alan@lxorguk.ukuu.org.uk, Dave Jones <davej@suse.de>,
karym@opersys.com, lmcmpou@lmc.ericsson.se,
lmcleve@lmc.ericsson.se
Subject: Re: Event logging vs enhancing printk
Date: 11 Apr 2002 11:11:00 -0400 [thread overview]
Message-ID: <m2ofgqtgmz.fsf@m3.polymtl.ca> (raw)
In-Reply-To: <m2it71uf4u.fsf@m3.polymtl.ca> <1018385394.7923.26.camel@w-beattie1>
> It would be easier, to fix the printk's, than to put evlogging into any
> particular piece of the kernel.
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!
next prev parent reply other threads:[~2002-04-11 14:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 23:18 Event logging vs enhancing printk Martin J. Bligh
2002-04-08 22:38 ` Andrew Morton
2002-04-08 23:54 ` Martin J. Bligh
2002-04-08 23:07 ` Andrew Morton
2002-04-09 2:14 ` Martin J. Bligh
2002-04-10 1:23 ` Andrea Arcangeli
2002-04-10 5:28 ` Martin J. Bligh
2002-04-11 0:15 ` Andrea Arcangeli
2002-04-09 14:34 ` Bill Davidsen
2002-04-09 14:50 ` Martin J. Bligh
2002-04-09 13:24 ` Denis Vlasenko
2002-04-09 14:42 ` Martin J. Bligh
2002-04-09 18:17 ` John Alvord
2002-04-09 14:21 ` Michel Dagenais
2002-04-09 20:49 ` Brian Beattie
2002-04-09 21:16 ` Martin J. Bligh
2002-04-09 22:28 ` Brian Beattie
2002-04-10 0:29 ` Brian Beattie
2002-04-10 1:17 ` Martin J. Bligh
2002-04-10 11:24 ` Denis Vlasenko
2002-04-11 15:11 ` Michel Dagenais [this message]
[not found] <OF7FF94B66.91DD315B-ON88256B95.00811EF0@boulder.ibm.com>
2002-04-10 8:21 ` Zoltan Menyhart
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 13:08 Michael Holzheu
[not found] <OF58E93BB4.1862769F-ON85256B97.0047811A@pok.ibm.com>
2002-04-10 14:19 ` sullivan
2002-04-10 15:55 Larry Kessler
2002-04-10 17:13 Francois-Xavier Kowalski
2002-04-10 19:43 Larry Kessler
[not found] <Pine.LNX.4.33.0204111358000.20722-100000@coffee.psychology.mcmaster.ca>
2002-04-12 9:30 ` Zoltan Menyhart
2002-04-12 12:41 ` Mark Hahn
2002-04-12 14:38 ` Martin J. Bligh
2002-04-12 18:04 ` Karim Yaghmour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ofgqtgmz.fsf@m3.polymtl.ca \
--to=michel.dagenais@polymtl.ca \
--cc=J.Bligh@m3.polymtl.ca \
--cc=Martin@m3.polymtl.ca \
--cc=Tony.P.Lee@nokia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alchemy@us.ibm.com \
--cc=davej@suse.de \
--cc=karym@opersys.com \
--cc=kessler@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmcleve@lmc.ericsson.se \
--cc=lmcmpou@lmc.ericsson.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.