On 24 May 2012 15:55, Rayson Ho <[email protected]> wrote: > On Wed, May 23, 2012 at 11:47 AM, Mark Dixon <[email protected]> wrote: >> How are you mapping existing queue limits to cgroup limits? >> memory.limit_in_bytes fits nicely onto h_rss (thanks for the suggestion >> William), but the crucially important memory.memsw.limit_in_bytes (rss+swap) >> doesn't seem to have an existing concept. Unless you're hijacking h_vmem? > > It's not really hijacking h_vmem - in the end, your memsw limit is the > virtual size limit of the process/job. > > >> When/were you thinking of open sourcing it? > > Open Grid Scheduler is "commercial open source", so when we ship GE > 2011.11 update 1, you will get the source. We are only selling > *optional* support, we don't sell our code under a commercial license, > see: > > http://www.scalablelogic.com/scalable-grid-engine-support > > >> I've got a new cluster coming online, so now is my main chance of changing >> user behaviour before the next machine that comes along. Sadly, I suspect >> that the ScalableLogic code will be too late for it. >> >> Is there some way we can collaborate on this one? > > There are 2 issues that we need to solve first: > > 1) Copyright assignment - like any other open source projects, we do > need to own the rights or else it is not safe for ISVs to use our > code. So far, the external contributions are smaller and quite
I'm pretty certain that there are open source projects that manage without this. There's an obscure little project called Linux that only requires knowledge of the code's provenance and compatible licensing. In any case don't Oracle own most of the Grid engine code or is that something else you're going to be announcing? I think even the prince of darkness ^W^W^W^W Univa has been know to accept contributions without copyright assignment. William _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
