[torqueusers] Memory resource limits and rlimits on Linux

"Mgr. Šimon Tóth" SimonT at mail.muni.cz
Thu Oct 14 08:09:41 MDT 2010

> 1. mom_over_limit()  in src/resmom/linux/mom_mach.c does NOT check
> "mem", only vmem and pvmem. The patch that Anton Starikov attached to
> the old thread did not make it into the source tree.

What system? Linux node does check mem. See mom_set_limits().

> 2. When setting mem, pmem, vmem, pvmem in the Torque script, only
> "pmem" actually gets translated into an rlimit ("data"). The other
> three resources (mem, vmem, and pvmem) are ignored. If I understand
> correctly, that's correct behavior for mem and vmem, which are summed
> limits over all processes in the job. But I would have thought setting
> pvmem would have set the address space (aka virtual memory) limit.

On Linux all four should be enforced. Limit gets stored into vmem_limit
and mem_limit and then enforced.

> 3. While torque does cancel a job if it runs over its walltime
> request, torque does nothing about jobs which run over their mem
> request. It leaves that to the scheduler to cancel.

Well, they shouldn't run over the limits in the first place.

Mgr. Šimon Tóth

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3366 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.supercluster.org/pipermail/torqueusers/attachments/20101014/31095bf5/attachment.bin 

More information about the torqueusers mailing list