On Fri, Jun 16, 2000 at 03:21:19PM -0500, Sam Watters wrote:
> I agree, providing resource limits will require additional hooks beyond fork and
> exit. Our initial goal was to provide a job container in support of job
> accounting. The next step is to develop resource limits.
>
> We have held off on the resource limits because that tends to be a problem area
> (as we have experienced when developing job based resource limits on IRIX). I
> foresee the following problems that must be addressed as job based resource
> limits are implemented.
>
> 1. How to handle the counting of shared memory pages. This has been an
> extremely difficult problem on IRIX to get right - in fact, it is still not done
> correctly.
All VM pages would be probably left out in the first implementation;
it requires lots of infrastructure in the VM that just isn't there yet. They
aren't that critical because they can be swapped out anyways. I'm looking
primarily for a solution of limiting pinned down buffers (like network buffers)
per user/group/job/login in.
> 3. How to handle resource limits in the context of "cluster" jobs.
You mean resource management in a beowulf ?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:12 EST