From: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
To: Jay Lan <jlan@sgi.com>
Cc: "Guillaume Thouvenin" <guillaume.thouvenin@bull.net>,
"Tim Schmielau" <tim@physik3.uni-rostock.de>,
"Arthur Corliss" <corliss@digitalmages.com>,
"Andrew Morton" <akpm@osdl.org>, "Jay Lan" <jlan@engr.sgi.com>,
lkml <linux-kernel@vger.kernel.org>,
erikj@dbear.engr.sgi.com, limin@engr.sgi.com,
lse-tech@lists.sourceforge.net,
"Ragnar Kjørstad" <kernel@ragnark.vestdata.no>,
"Yoshitaka ISHIKAWA" <y.ishikawa@soft.fujitsu.com>
Subject: Re: [Lse-tech] Re: [PATCH] new CSA patchset for 2.6.8
Date: Tue, 31 Aug 2004 11:06:47 +0200 [thread overview]
Message-ID: <20040831090647.GA3441@frec.bull.fr> (raw)
In-Reply-To: <412F9197.4030806@sgi.com>
On Fri, Aug 27, 2004 at 12:55:03PM -0700, Jay Lan wrote:
> Please visit http://oss.sgi.com/projects/pagg/
> The page has been updated to provide information on a per job
> accounting project called 'job' based on PAGG.
>
> There is one userspace rpm and one kernel module for job.
> This may provide what you are looking for. It is a mature product
> as well. I am sure Limin(job) and Erik(pagg) would appreciate any
> input you can provide to make 'job' more useful.
I have a question about job. If I understand how it works, you can not
add a process in a job. I mean when you start a session, a container is
created and it's the only way to create it. If I'm right, I think that it
could be interesting to add a process using ioctl and /proc interface. For
example, if I want to know how resources are used by a compilation, I
need to add the process gcc in a container. Any comments?
Best,
Guillaume
next prev parent reply other threads:[~2004-08-31 9:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 0:25 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
2004-08-31 14:19 ` Tim Schmielau
2004-08-31 23:01 ` [Lse-tech] " Jay Lan
2004-09-08 18:32 ` Jay Lan
2004-08-28 1:26 ` Arthur Corliss
[not found] ` <20040827054218.GA4142@frec.bull.fr>
2004-08-27 19:31 ` [Lse-tech] " John Hesterberg
2004-08-30 8:29 ` Tim Schmielau
2004-08-27 19:55 ` Jay Lan
2004-08-31 9:06 ` Guillaume Thouvenin [this message]
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-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=20040831090647.GA3441@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=jlan@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 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®