From: Chris Friesen <chris.friesen@windriver.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: per-NUMA memory limits in mem cgroup?
Date: Mon, 23 Apr 2018 11:29:21 -0400 [thread overview]
Message-ID: <5ADDFBD1.7010009@windriver.com> (raw)
In-Reply-To: <20180422124648.GD17484@dhcp22.suse.cz>
On 04/22/2018 08:46 AM, Michal Hocko wrote:
> On Fri 20-04-18 11:43:07, Chris Friesen wrote:
>> 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?
I'd envision it working exactly the same as the current memory cgroup, but with
the ability to specify optional per-NUMA-node limits in addition to system-wide.
Chris
next prev parent reply other threads:[~2018-04-23 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 17:43 per-NUMA memory limits in mem cgroup? Chris Friesen
2018-04-22 12:46 ` Michal Hocko
2018-04-23 15:29 ` Chris Friesen [this message]
2018-04-24 13:27 ` Michal Hocko
2018-04-24 15:13 ` Chris Friesen
2018-04-24 15:23 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ADDFBD1.7010009@windriver.com \
--to=chris.friesen@windriver.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.