On Fri 20-04-18 11:43:07, Chris Friesen wrote: > Hi, > > I'm aware of the ability to use the memory controller to limit how much > memory a group of tasks can consume. > > Is there any way to limit how much memory a group of tasks can consume *per > NUMA node*? Not really. We have all or nothing via cpusets but nothing really fine grained for the amount of memory. > The specific scenario I'm considering is that of a hypervisor host. I have > system management stuff running on the host that may need more than one > core, and currently these host tasks might be affined to cores from multiple > NUMA nodes. I'd like to put a cap on how much memory the host tasks can > allocate from each NUMA node in order to ensure that there is a guaranteed > amount of memory available for VMs on each NUMA node. > > Is this possible, or are the knobs just not there? Not possible right now. What would be the policy when you reach the limit on one node? Fallback to other nodes? What if those hit the limit as well? OOM killer or an allocation failure? -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
