Page Comparison

...

• Synopsis: cgroup.cpuset.mem_fences
• Detail: Allow administrator to prevent cgroup hook from binding jobs to NUMA nodes. This prevents the hook from writing values to cpuset.mems in the cpuset subsystem.
• Default: True, cgroup hook will write values to cpuset.mems.

• Example:

  Code Block
  title excludemem_cpusfences
  "cpuset" : { "enabled" : true, "mem_fences" : true, "exclude_hosts" : ["node004"], "exclude_vntypes" : ["green_node"] },

  
  

...

• Synopsis: cgroup.cpuset.mem_hardwall
• Detail: Allow administrator to override the value of cpuset.mem_hardwall. The RedHat documentation discribes this as:

  cpuset.mem_hardwall

  contains a flag (0 or 1) that specifies whether kernel allocations of memory page and buffer data should be restricted to the memory nodes specified for the cpuset. By default (0), page and buffer data is shared across processes belonging to multiple users. With a hardwall enabled (1), each tasks' user allocation can be kept separate.

• Default: False (zero)

• Example:

  Code Block
  title excludemem_cpushardwall
  "cpuset" : { "enabled" : true, "mem_hardwall" : false, "exclude_hosts" : ["node004"], "exclude_vntypes" : ["green_node"] },

  
  

...

• Synopsis: cgroup.cpuset.memory_spread_page
• Detail: Allow administrator to override the value of cpuset.memory_spread_page. The RedHat documentation discribes this as:

  cpuset.memory_spread_page

  contains a flag (0 or 1) that specifies whether file system buffers should be spread evenly across the memory nodes allocated to the cpuset. By default (0), no attempt is made to spread memory pages for these buffers evenly, and buffers are placed on the same node on which the process that created them is running.

• Default: False (zero)

• Example:

  Code Block
  title excludememory_spread_cpuspage
  "cpuset" : { "enabled" : true, "memory_spread_page" : false, "exclude_hosts" : ["node004"], "exclude_vntypes" : ["green_node"] },

  
  

...