[Mauiusers] Question on mem resource differences between torque and maui

Dave Jackson jacksond at clusterresources.com
Tue Feb 7 11:58:03 MST 2006


Ake,

  You are correct.  The technically correct use of these constraints
first needs to be clarified in the TORQUE documentation and then we need
to enhance Maui to support the concept of 'per node' dedicated resource
limits.  It currently has per task and per job dedicated resource limits
and per node requirements specification (ie, only allocate nodes with at
least X memory configured)

  This will take some work.

Dave

On Tue, 2006-02-07 at 14:01 +0100, Åke Sandgren wrote:
> Hi!
> 
> In MPBSI.c MPBSJobSetAttr there is the following code
> 
> ================
>   else if (!strcmp(AP->name,ATTR_l))
>     {
> ...
>     else if (!strcmp(AP->resource,"pmem"))
>       {
>       /* NOTE: called 'workingset'? (indiana) */
> 
>       /* 'per processor' required memory */
> 
>       RQ->DRes.Mem = (MPBSGetResKVal(AP->value) >> 10);
>       }
>     else if (!strcmp(AP->resource,"pvmem"))
>       {
>       /* NOTE: called 'pmem'? (indiana) */
> 
>       /* 'per processor' required swap */
> 
>       RQ->DRes.Swap = (MPBSGetResKVal(AP->value) >> 10);
>       }
>     else if (!strcmp(AP->resource,"mem"))
>       {
>       /* 'per job' required memory */
> 
>       TA->JobMemLimit = (MPBSGetResKVal(AP->value) >> 10);
>       }
>     else if (!strcmp(AP->resource,"vmem"))
>       {
>       /* 'per job' required swap */
> 
>       TA->JobSwapLimit = (MPBSGetResKVal(AP->value) >> 10);
>       }
> ===================
> 
> This looks weird after having read at least the linux/mom_mach.c from
> torque where p(v)mem is limited per process (not processor) and (v)mem
> is limited per node (or task) not per job.
> 
> Dave? Garrick?
> 



More information about the mauiusers mailing list