> What do you want to do with them? (They're not without problems.) I'm already playing with them on my desktop machine since a few months, and I just want to experiment the use of cgroup within SGE.
I'd like to prevent job eating more than X% of ram+swap using : memory.limit_in_bytes # set/show limit of memory usage memory.memsw.limit_in_bytes # set/show limit of memory+Swap usage > The prolog is no use, as such, because it only runs on the master node, > and isn't connected to the shepherd. Ok, I should have understand that. > There is preliminary cpuset support in the current SGE (though there's a > bug report of problems I haven't got to the bottom of) and Mark Dixon > has posted patches whose functionality will get merged soon. Ok. > Look in the current SGE source (which has been partly restructured, but > that's not finished and published), and also in the source of SLURM, and > possibly Condor. I've cloned the current trunk of the subversion repository, but I didn't see anything. Maybe in a specific branch, I'll look around. >From the blog post I read, I thought it was already in 2011p1, hence the confusion. > If you want to work on it, I'm happy to make suggestions for > contributions to SGE (and Mark probably will), bearing in mind much of > the work is already done. The main issue, apart from cgroups being a > moving target with their own problems, is actually providing a good > user/admin interface, at least in the current SGE style. I'm too lazy (and not really the right guy) =) Thank you for your answer. _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
