From: Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca>
To: Erik Jacobson <erikj@subway.americas.sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Process Aggregates (PAGG) support for the 2.6 kernel
Date: Fri, 30 Apr 2004 10:54:29 +0200 [thread overview]
Message-ID: <1083315269.409214456f48d@www.imp.polymtl.ca> (raw)
In-Reply-To: <Pine.SGI.4.53.0404261656230.591647@subway.americas.sgi.com>
Selon Erik Jacobson <erikj@subway.americas.sgi.com>:
> What is Process Aggregates (PAGG)?
> ----------------------------------
> PAGG provides for the implementation of arbitrary process groups in Linux.
> It is a building block for kernel modules that can group processes
> together into a single set for specific purposes beyond the traditional
> process groups.
Hello,
I'm working on a project (ELSA -Enhanced Linux System Accounting) that is
very similar to PAGG and CSA. My goal is to improve accounting on Linux by using
containers to group processes according to the system administrator policy.
Currently I provide a patch to 2.6.5 kernel ( http://elsa.sourceforge.net ) that
provides infrastructures to manipulate containers. The advantage of my patch is
that manipulating containers is very simple. I think that it could be very
interesting to share our work to see what could be done. Thus I will take a look
to PAGG implementation and also to the CKRM solution proposed by Chris Wright.
Best,
Guillaume
next prev parent reply other threads:[~2004-04-30 8:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 22:04 Erik Jacobson
2004-04-26 23:39 ` Chris Wright
2004-04-27 0:36 ` Jesse Barnes
2004-04-27 0:41 ` Chris Wright
2004-04-27 21:00 ` Erik Jacobson
2004-04-27 21:05 ` Chris Wright
2004-04-29 21:10 ` Rik van Riel
2004-04-27 20:51 ` Erik Jacobson
2004-04-27 22:28 ` Chris Wright
2004-04-28 14:55 ` Christoph Hellwig
2004-04-29 19:20 ` Paul Jackson
2004-04-29 19:27 ` Chris Wright
2004-04-29 19:29 ` Christoph Hellwig
2004-04-29 19:34 ` Paul Jackson
2004-04-29 19:53 ` Erik Jacobson
2004-04-29 21:20 ` Rik van Riel
2004-04-30 6:17 ` Christoph Hellwig
2004-04-30 11:08 ` Guillaume Thouvenin
2004-04-30 18:00 ` Shailabh
2004-04-30 18:28 ` Rik van Riel
2004-04-30 12:54 ` Rik van Riel
2004-04-30 13:06 ` Christoph Hellwig
2004-04-30 13:28 ` Chris Mason
2004-04-30 16:50 ` Shailabh
2004-04-30 15:22 ` Rik van Riel
2004-04-30 16:45 ` Christoph Hellwig
2004-04-30 17:53 ` Shailabh
2004-04-30 18:15 ` Chris Wright
2004-04-30 15:59 ` Chris Wright
2004-04-30 8:54 ` Guillaume Thouvenin [this message]
2004-05-20 21:16 ` Erik Jacobson
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=1083315269.409214456f48d@www.imp.polymtl.ca \
--to=guillaume.thouvenin@polymtl.ca \
--cc=erikj@subway.americas.sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome