From: Michal Hocko <mhocko@kernel.org>
To: Shuah Khan <shuah@kernel.org>
Cc: Will Deacon <will.deacon@arm.com>,
catalin.marinas@arm.com, sudeep.holla@arm.com,
ganapatrao.kulkarni@cavium.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: add NUMA emulation support
Date: Fri, 7 Sep 2018 10:34:52 +0200 [thread overview]
Message-ID: <20180907083452.GC19621@dhcp22.suse.cz> (raw)
In-Reply-To: <c1b58f13-6190-20e9-7e4f-b8bc2b9d5f80@kernel.org>
On Thu 06-09-18 15:53:34, Shuah Khan wrote:
[...]
> A few critical allocations could be satisfied and root cgroup prevails. It is not the
> intent to have exclusivity at the expense of the kernel.
Well, it is not "few critical allocations". It can be a lot of
memory. Basically any GFP_KERNEL allocation. So how exactly you expect
this to work when you cannot estimate how much
memory will kernel eat?
>
> This feature will allow a way to configure cpusets on non-NUMA for workloads that can
> benefit from the reservation and isolation that is available within the constraints of
> exclusive cpuset policies.
AFAIR this was the first approach Google took for the memory isolation
and they moved over to memory cgroups. I would recommend to talk to
those guys bebfore you introduce potentially a lot of code that will not
really work for the workload you indend it for.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-09-07 8:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 23:05 Shuah Khan (Samsung OSG)
2018-08-28 17:40 ` Will Deacon
2018-08-28 18:09 ` Shuah Khan
2018-08-29 11:08 ` Michal Hocko
2018-09-04 21:59 ` Shuah Khan
2018-09-05 6:42 ` Michal Hocko
2018-09-06 21:53 ` Shuah Khan
2018-09-07 8:34 ` Michal Hocko [this message]
2018-09-07 22:30 ` Shuah Khan
2018-09-10 13:48 ` Michal Hocko
2018-09-11 2:02 ` Shuah Khan
2018-09-11 9:11 ` Michal Hocko
2018-09-11 15:27 ` Shuah Khan
2018-09-11 16:50 ` Will Deacon
2018-09-11 19:53 ` Shuah Khan
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=20180907083452.GC19621@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=ganapatrao.kulkarni@cavium.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®