From: Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca>
To: Jay Lan <jlan@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
Christoph Lameter <clameter@sgi.com>,
torvalds@osdl.org, linux-kernel@vger.kernel.org,
guillaume.thouvenin@bull.net
Subject: Re: move-accounting-function-calls-out-of-critical-vm-code-paths.patch
Date: Tue, 8 Feb 2005 11:11:41 +0100 [thread overview]
Message-ID: <1107857501.4208905d3f019@www.imp.polymtl.ca> (raw)
In-Reply-To: <42077724.1060606@sgi.com>
Selon Jay Lan <jlan@sgi.com>:
> CSA is currently implemented as a loadable module. I think ELSA is the
> same, right? The use of the enhanced accounting data collection
> code is not in the kernel tree. That was why Andrew did not see usage of
> the accounting patches. Should i propose to include the CSA module in
> the kernel then, Andrew? :)
In fact there is a module in ELSA but it's just to keep a trace of the processes
hierarchy in order to do processes group management and process group
accounting in user space.
The process group management is done by a user space daemon and the process
group accounting is done by a user space application that computes information
provided by BSD-per process accounting and/or CSA accounting with information
provided by the user space daemon.
Thus currently there is a module that relays information about forks but I'm
working on a kobject_uevent solution to send the fork event (thanks to Andrew
for the suggestion).
Thus, I will be interesting to see CSA module in the kernel.
Regards,
Guillaume
next prev parent reply other threads:[~2005-02-08 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050110184617.3ca8d414.akpm@osdl.org>
[not found] ` <Pine.LNX.4.58.0502031319440.25268@schroedinger.engr.sgi.com>
[not found] ` <20050203140904.7c67a144.akpm@osdl.org>
2005-02-03 22:45 ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Christoph Lameter
2005-02-03 23:05 ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Andrew Morton
2005-02-04 0:41 ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Tim Schmielau
2005-02-04 7:38 ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Guillaume Thouvenin
2005-02-07 14:11 ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Jay Lan
2005-02-07 22:57 ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Andrew Morton
2005-02-08 10:11 ` Guillaume Thouvenin [this message]
2005-02-03 21:22 move-accounting-function-calls-out-of-critical-vm-code-paths.patch Christoph Lameter
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=1107857501.4208905d3f019@www.imp.polymtl.ca \
--to=guillaume.thouvenin@polymtl.ca \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=guillaume.thouvenin@bull.net \
--cc=jlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
Powered by JetHome