From: Shuah Khan <shuah@kernel.org>
To: Michal Hocko <mhocko@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, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] arm64: add NUMA emulation support
Date: Mon, 10 Sep 2018 20:02:05 -0600 [thread overview]
Message-ID: <4d7beb50-f778-507a-4c3c-f6de92f8cfb9@kernel.org> (raw)
In-Reply-To: <20180910134845.GH10951@dhcp22.suse.cz>
Hi Michal,
On 09/10/2018 07:48 AM, Michal Hocko wrote:
> On Fri 07-09-18 16:30:59, Shuah Khan wrote:
>> On 09/07/2018 02:34 AM, Michal Hocko wrote:
>>> On Thu 06-09-18 15:53:34, Shuah Khan wrote:
[....]
>>
>> In addition to isolation, being able to reserve a block instead is one of the
>> issues I am looking to address. Unfortunately memory cgroups won't address that
>> issue.
>
> Could you be more specific why you need reservations other than
> isolation.
>
Taking automotive as a specific example, there are two classes of applications:
1. critical applications that must run
2. Infotainment and misc. user-space.
In this case, being able to reserve a block of memory for critical applications
will ensure the memory is available for them. If a critical application has to
restart and/or when an on-demand critical application starts, it might not be able
to allocate memory if it is not reserved.
When a flat system has multiple memory blocks, with NUMA emulation in conjunction with
cpusets, one or more block can be reserved for critical applications configuring a set
of cpus and one of more memory nodes for them.
Memory cgroups will not support such reservation. Hope this helps explain the use-case
I am trying to address with this patch.
thanks,
-- Shuah
next prev parent reply other threads:[~2018-09-11 2:02 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
2018-09-07 22:30 ` Shuah Khan
2018-09-10 13:48 ` Michal Hocko
2018-09-11 2:02 ` Shuah Khan [this message]
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=4d7beb50-f778-507a-4c3c-f6de92f8cfb9@kernel.org \
--to=shuah@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=mhocko@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®