-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/11/12 01:43, Ralph Castain wrote:
> On Nov 4, 2012, at 7:28 PM, Christopher Samuel > <sam...@unimelb.edu.au> wrote: > >> I would argue that the resource managers *should* be doing it > > No argument from me - I would love for them to provide me with an > easy API that mpirun can use to specify the requirements for a > given application. Wouldn't it be the other way around with the resource manager setting limits and then having the job run inside it? Basically like the current cpuset support in Torque, et. al, but on steroids. That way mpirun and/or orted could learn from the kernel the details of the cgroup it is in and arrange itself appropriately. I believe that Slurm has some support for cgroups already: http://www.schedmd.com/slurmdocs/cgroups.html [memcg performance] > Yick! However, I would expect the community to reduce that impact > over time. If systems don't want that capability, then they can > and should disable it. On the other hand, if they do want it, then > we want to support it. Indeed! cheers, Chris - -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCYReYACgkQO2KABBYQAh+BxQCbB1lbNCqotuA2paV+G6+cfAdP xxwAnAurUX8OoK1+4oJJJY7NV9cmIoRV =yrCv -----END PGP SIGNATURE-----
