[torquedev] mem limit change in resmon/linux/mom_mach.c

Dave Jackson jacksond at clusterresources.com
Tue Apr 25 16:39:54 MDT 2006


Garrick,

  The rationale was this.  mem only applied to total job memory
consumption while pmem applied to individual node memory consumption.
Some sites had users using mem with serial jobs and this wasn't being
enforced by the mom.  Thus, for serial jobs, they wanted mem to map to
pmem.

  The part about breaking something was probably not intended.  I will
make a change to fix this.

Dave  

On Tue, 2006-04-25 at 15:36 -0700, Garrick Staples wrote:
> Does anyone know the rationale for this change in
> resmon/linux/mom_mach.c?
> 
> @@ -1251,11 +1259,8 @@ int mom_set_limits(
>            vmem_limit = value;
>          }
>        } 
> -    else if (strcmp(pname,"mem") == 0) 
> -      {        
> -      /* ignore */
> -      } 
> -    else if (strcmp(pname,"pmem") == 0) 
> +    else if ((!strcmp(pname,"mem") && (pjob->ji_numnodes == 1)) ||
> +              !strcmp(pname,"pmem")) 
>        {        
>        /* set */
>  
> 
> Using "mem" on multi-node jobs are now getting rejected as an unknown
> resource.
> 
> _______________________________________________
> torquedev mailing list
> torquedev at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torquedev



More information about the torquedev mailing list