All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca>
To: linux-kernel@vger.kernel.org
Subject: [Patch] Enhanced Linux System Accounting for 2.6.7
Date: Fri, 25 Jun 2004 07:19:10 +0200	[thread overview]
Message-ID: <1088140750.40dbb5ce0fd50@www.imp.polymtl.ca> (raw)

Hello,

    Here is a new patch for kernel 2.6.7. You can download it from 
sourceforge at 
http://prdownloads.sourceforge.net/elsa/patch-2.6.7-elsa?download
  
    This patch provides structures and functions to do accounting
for a group of process. There is two parts. 

  On one hand there is two APIs that allow the creation and the 
destruction of an item called a "bank" that will contain an 
group of processes. There is also two other routines that can 
add or remove processes in a bank.

  On the other hand, you have the accounting mechanism that used bank
to perform BSD-like accounting for a group of process. We used ioctl()
interface to create/destroy a bank and also to add/remove a process in
a bank. Currently, device driver is dev/elsacct and the major number
is dynamically allocated, therefore you need to check the number in the
/proc/devices and create the corresponding device. A sample code is
given at:
http://cvs.sourceforge.net/viewcvs.py/elsa/tests/elsa_cmd.c?rev=1.7&view=markup
 
    Currently we do BSD-like accounting. The next step is to identify what
kind of metrics can be interesting for accounting. We started to describe
that point on a withpaper that is available at:
http://sourceforge.net/docman/display_doc.php?docid=23446&group_id=105806
This paper describes differences between two accounting systems that are
ELSA and CSA.
 
    Every comments are welcome, 

The ELSA poject team (http://elsa.sourceforge.net)

                 reply	other threads:[~2004-06-25  5:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1088140750.40dbb5ce0fd50@www.imp.polymtl.ca \
    --to=guillaume.thouvenin@polymtl.ca \
    --cc=linux-kernel@vger.kernel.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 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.