From: Jay Lan <jlan@engr.sgi.com>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: "Andrew Morton" <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
erikj@dbear.engr.sgi.com, limin@engr.sgi.com,
lse-tech@lists.sourceforge.net,
"Ragnar Kjørstad" <kernel@ragnark.vestdata.no>,
"Yoshitaka ISHIKAWA" <y.ishikawa@soft.fujitsu.com>,
"Arthur Corliss" <corliss@digitalmages.com>,
"Guillaume Thouvenin" <guillaume.thouvenin@bull.net>
Subject: Re: [Lse-tech] Re: [PATCH] new CSA patchset for 2.6.8
Date: Thu, 26 Aug 2004 11:26:51 -0700 [thread overview]
Message-ID: <412E2B6B.80904@engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0408261821090.14826@gockel.physik3.uni-rostock.de>
The reason for breaking up one CSA patch into four patches was
so that the only CSA (http://oss.sgi.com/projects/csa/) specific
thing is the csa_module. My intention is to improve the system
accounting data collection and make the data available to any
clients that can use the data. The three areas of accounting
data we try to improve are io, mm, and per-process area.
As Tim said the problem of BSD accounting was that it has been
inactive for a long time. I do not mind incoporating the
three accounting data collection patches i submitted into BSD or
others as long as the data made available to modules that plan
to make use of the data. :)
Thanks,
- jay
Tim Schmielau wrote:
> On Wed, 25 Aug 2004, Andrew Morton wrote:
>
>
>>More broadly: Help!
>>
>>I am 100% not in a position to judge whether Linux needs Comprehensive
>>System Accounting, nor am I able to define what the requirements for such a
>>thing should be. All I can tell from your patch is the quality of its
>>implementation, and that's leaping far, far ahead of where we should be.
>>
>>We're going to need help from you, and from all the other stakeholders in
>>judging how useful this feature is to Linux implementors and how well this
>>implementation meets the (unknown) requirements. See my problem?
>>
>>I've cc'ed lse-tech, where enterprise folks hang out. I would request that
>>the people who are stakeholders in this feature
>>
>>a) stick their hands up
>>
>>b) let us know how important this kind of feature is for their users
>>
>>c) review the offered feature set against their requirements
>>
>>d) let us know how well the implementation fits that requirement and
>>
>>e) inform us of any competing implementations. Compare and contrast.
>
>
> Judging from the feedback during it's stay in -mm (none at all!), general
> interest in BSD accounting seems quite limited. The rate of downloads of
> the updated userspace tools is hardly distinguishable from background
> noise. (This might change with the correct URL in the help text now, but
> even that was broken for months and nobody cared).
> Also general interest in the user space tools is low, the latest release
> of the GNU acct package is from 1998 (and yes, there _are_ problems
> warranting updates).
>
> Funnily enough, with three competing implementation even interest from
> developers seems larger than that from users (This statement includes me,
> I did a patch but am not a user of it).) But communication between
> developers is poor. I for myself only recently learned about ELSA and CSA.
>
> Therefore I've Cc:ed some people from whom I got valuable feedback on the
> BSD accounting format patch.
>
> IMHO CSA, ELSA and BSD accounting are too similar to have more than one of
> them in the kernel. We should either improve BSD accounting to do the job,
> or kill it in favor of a different implementation.
>
> Tim
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Lse-tech mailing list
> Lse-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lse-tech
next prev parent reply other threads:[~2004-08-26 18:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 0:25 [PATCH] new CSA patchset for 2.6.8 Jay Lan
2004-08-26 5:18 ` Andrew Morton
2004-08-26 17:15 ` Tim Schmielau
2004-08-26 18:26 ` Jay Lan [this message]
2004-08-26 19:44 ` [Lse-tech] " Arthur Corliss
2004-08-26 18:43 ` John Hesterberg
2004-08-27 8:26 ` Tim Schmielau
2004-08-26 19:24 ` Arthur Corliss
2004-08-26 20:05 ` Tim Schmielau
2004-08-26 20:46 ` Jay Lan
2004-08-28 1:27 ` Arthur Corliss
2004-08-30 12:26 ` Guillaume Thouvenin
2004-08-31 14:19 ` Tim Schmielau
2004-08-31 23:01 ` [Lse-tech] " Jay Lan
2004-09-08 18:32 ` Jay Lan
[not found] ` <20040827054218.GA4142@frec.bull.fr>
2004-08-27 19:31 ` John Hesterberg
2004-08-30 8:29 ` Tim Schmielau
2004-08-27 19:55 ` Jay Lan
2004-08-31 9:06 ` Guillaume Thouvenin
2004-08-31 10:29 ` Guillaume Thouvenin
2004-08-31 16:04 ` Limin Gu
2004-09-01 21:44 ` John Hesterberg
2004-08-28 1:33 ` Arthur Corliss
2004-08-28 1:26 ` Arthur Corliss
2004-08-26 18:38 ` [Lse-tech] " John Hesterberg
[not found] ` <412EADBC.60607@bigpond.net.au>
[not found] ` <20040826205349.0582d38e.akpm@osdl.org>
2004-08-27 20:24 ` Jay Lan
2004-08-30 19:10 ` John Hesterberg
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=412E2B6B.80904@engr.sgi.com \
--to=jlan@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=corliss@digitalmages.com \
--cc=erikj@dbear.engr.sgi.com \
--cc=guillaume.thouvenin@bull.net \
--cc=kernel@ragnark.vestdata.no \
--cc=limin@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=tim@physik3.uni-rostock.de \
--cc=y.ishikawa@soft.fujitsu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox