From: Andrew Morton <akpm@osdl.org>
To: Jay Lan <jlan@sgi.com>
Cc: linux-kernel@vger.kernel.org, guillaume.thouvenin@bull.net,
tim@physik3.uni-rostock.de, kaigai@ak.jp.nec.com,
jbarnes@sgi.com
Subject: Re: [PATCH 2.6.11-rc4-mm1] end-of-proces handling for acct-csa
Date: Thu, 24 Feb 2005 20:46:46 -0800 [thread overview]
Message-ID: <20050224204646.704680e9.akpm@osdl.org> (raw)
In-Reply-To: <421EA8FF.1050906@sgi.com>
Jay Lan <jlan@sgi.com> wrote:
>
> Since my idea of providing an accounting framework was considered
> 'overkill', here i submit a tiny patch just to allow CSA to
> handle end-of-process (eop) situation by saving off accounting
> data before a task_struct is disposed.
>
> This patch is to modify the acct_process() in acct.c, which is
> invoked from do_exit() to handle eop for BSD accounting. Now
> the acct_process() wrapper will also take care of CSA, if it has
> been loaded. If the CSA module has been loaded, a CSA routine
> will be invoked to construct a CSA job record and to write the
> record to the CSA accounting file.
I really don't want to have to (and shouldn't need to) become an accounting
person, but as there seems to be a communication problem somewhere..
Please, you guys are the subject matter experts. Put your heads together
and come up with something.
We shouldn't be putting CSA stuff over here and ELSA stuff over there.
We should be putting our heads together and coming up with a sensible and
adequate accounting solution for Linux. Or the kernel, at least.
The ELSA team appear to be able to do that in userspace with the existing
process accounting machinery and a single outcall from fork(). That's great.
Why is that not adequate for CSA? What end-user features does CSA offer
that ELSA can not? Could those features be implemented (in userspace) if
we also added an exit() outcall?
next prev parent reply other threads:[~2005-02-25 4:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 4:26 Jay Lan
2005-02-25 4:46 ` Andrew Morton [this message]
2005-02-25 6:57 ` Guillaume Thouvenin
2005-02-28 18:56 ` Jay Lan
2005-03-01 7:33 ` Guillaume Thouvenin
2005-03-01 18:06 ` Jay Lan
2005-03-02 7:48 ` Guillaume Thouvenin
2005-03-02 17:56 ` Jesse Barnes
2005-03-02 17:59 ` Jay Lan
2005-03-05 6:29 ` Tim Schmielau
2005-03-07 23:57 ` Jay Lan
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=20050224204646.704680e9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=guillaume.thouvenin@bull.net \
--cc=jbarnes@sgi.com \
--cc=jlan@sgi.com \
--cc=kaigai@ak.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
/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
all inboxes | Powered by JetHome®