csa
[Top] [All Lists]

Re: Availability

To: John Logsdon <j.logsdon@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Availability
From: Erik Jacobson <erikj@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 15 Oct 2004 09:03:17 -0500
Cc: Robin Holt <holt@xxxxxxx>, csa@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.10.10410151437060.11065-100000@mercury.quantex>
References: <Pine.LNX.4.10.10410151437060.11065-100000@mercury.quantex>
Sender: csa-bounce@xxxxxxxxxxx
I read your not.  I'm still going to see what Jay says about this.  If
he thinks we need to bring the PAGG and JOB patches up to date for 2.4.x,
I'd be happy to work on that.

> Since CSA requires PAGG, in due course it would be appropriate to combine
> the patches but I guess you can always append the patch files and run it
> in one go.  What's the JOB patch?  I don't see it on the SGI project list.
> (Actually your ftp server seems to hang episodically, particularly on IE).

I don't know anything about the web site hanging - sorry.

But here is the project page for PAGG and Job:
http://oss.sgi.com/projects/pagg/

PAGG is sort of a generic patch for making kernel modules that need to
group processes together.  It provides callbacks that can notify your
kernel module when a process forks, execs, exits, etc.  It is not
specific to CSA - we have things at SGI that make use of PAGG but not
CSA and Job.

Job provides inescapable job containers.  It is one of the users of PAGG.
CSA uses both PAGG and Job.

Job on it's own could be useful, for example, for people writing batch
schedulers, where you want to track a job container that may contain multiple
processes and manage it (throttle it, etc).  Since a given job may need to
start other processes to do it's work, it is convenient to be able to
collect it together inside a container even if you're not interested in
running CSA.

I guess I'm trying to say that Job and especially PAGG stand on their own
for the most part...

I hope that helps.

Erik

<Prev in Thread] Current Thread [Next in Thread>