From: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
To: Arthur Corliss <corliss@digitalmages.com>
Cc: Jay Lan <jlan@engr.sgi.com>,
Tim Schmielau <tim@physik3.uni-rostock.de>,
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, ? <kernel@ragnark.vestdata.no>,
Yoshitaka ISHIKAWA <y.ishikawa@soft.fujitsu.com>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Subject: Re: [PATCH] new CSA patchset for 2.6.8
Date: Mon, 30 Aug 2004 14:26:14 +0200 [thread overview]
Message-ID: <20040830122614.GA2518@frec.bull.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0408271727020.1075@bifrost.nevaeh-linux.org>
On Fri, Aug 27, 2004 at 05:27:19PM -0800, Arthur Corliss wrote:
> On Thu, 26 Aug 2004, Jay Lan wrote:
>
> > I do like to see a common data collection method in the kernl. Kernel
> > does not need to decide how the data to be presented to the
> > user space. An accounting loadable module such as CSA or ELSA will
> > take care of how the data to be presented to meet the needs of
> > different users.
> >
> > Sounds reasonable?
>
> Seconded.
Thus, to be clear, the enhanced accounting can be divided into
three parts:
1) A common data collection method in the kernel.
We could start from BSD-accounting and add CSA information. Could
it be something like BSD version4?
2) A module that will manage a job history. I mean, it will manage a
structure in which we will keep the relationship between processes and
"containers" and also between process and its children. The
property needed here is that a child belongs to the same "job"
as its parent. This allows to do per-job accounting. I will have
a look to PAGG and JOB.
Can it be done in userspace? Is the lost of data (as observed by
Arthur Corliss with SAR) can be avoided?
3) Finally we need module that will be in charge of datas
presentation. This will allow to be easily compatible with other
applications.
I will have a look to the per-job accounting patch. If I understand
well, this patch falls into the second requirement (manage groups of
processes).
Regards,
Guillaume
next prev parent reply other threads:[~2004-08-30 12:28 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 ` [Lse-tech] " Jay Lan
2004-08-26 19:44 ` 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 [this message]
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=20040830122614.GA2518@frec.bull.fr \
--to=guillaume.thouvenin@bull.net \
--cc=akpm@osdl.org \
--cc=corliss@digitalmages.com \
--cc=erikj@dbear.engr.sgi.com \
--cc=jlan@engr.sgi.com \
--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 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.