On Wed, 30 May 2012, Mark Dixon wrote:
Hi Rayson,
Sorry to sound needy, but have you had time to consider controlling
cgroup's memory.memsw.limit_in_bytes via a new attribute defined as the
OS-dependent way to measure memory usage (typically RAM+swap), rather than
overloading h_vmem/s_vmem?
Keeping things separate should help greatly in improving the utilisation
of clusters, which keeps everyone happy.
I'm guessing it is getting rather close to your u2 release now, but from
what you've told me, it sounds like this work is an extension to what
you've done and doesn't need to hold it up?
In case you missed it, here's the nub of what I've previously said:
...
Whoops, just re-read that and realised it could be misconstrued.
Just to make clear: this isn't about me wanting to get others to write
code, this is about trying to get agreement about how a gridengine feature
should look and behave to the user.
I'm still continuing with my patchset, and will post it publicly, because
the cluster I'm putting in now needs cgroup memory control and an
independently set h_vmem. I hope to ditch the patchset once the
ScalableLogic code becomes the norm, as it sounds like a cleaner
implementation.
I'm provisionally using the name h_mem / s_mem to control cgroup memory
enforcement, but am willing to be argued into changing this.
Best wishes,
Mark
--
-----------------------------------------------------------------
Mark Dixon Email : [email protected]
HPC/Grid Systems Support Tel (int): 35429
Information Systems Services Tel (ext): +44(0)113 343 5429
University of Leeds, LS2 9JT, UK
-----------------------------------------------------------------
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
