From: Xishi Qiu <qiuxishi@huawei.com>
To: "Izumi, Taku" <izumi.taku@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"Kamezawa, Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"mel@csn.ul.ie" <mel@csn.ul.ie>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"dave.hansen@intel.com" <dave.hansen@intel.com>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>
Subject: Re: [PATCH] mm: Introduce kernelcore=reliable option
Date: Tue, 20 Oct 2015 09:42:23 +0800 [thread overview]
Message-ID: <56259BFF.1090203@huawei.com> (raw)
In-Reply-To: <E86EADE93E2D054CBCD4E708C38D364A5427FECE@G01JPEXMBYT01>
On 2015/10/20 8:34, Izumi, Taku wrote:
> Hi Xishi,
>
>> On 2015/10/15 21:32, Taku Izumi wrote:
>>
>>> Xeon E7 v3 based systems supports Address Range Mirroring
>>> and UEFI BIOS complied with UEFI spec 2.5 can notify which
>>> ranges are reliable (mirrored) via EFI memory map.
>>> Now Linux kernel utilize its information and allocates
>>> boot time memory from reliable region.
>>>
>>> My requirement is:
>>> - allocate kernel memory from reliable region
>>> - allocate user memory from non-reliable region
>>>
>>> In order to meet my requirement, ZONE_MOVABLE is useful.
>>> By arranging non-reliable range into ZONE_MOVABLE,
>>> reliable memory is only used for kernel allocations.
>>>
>>> This patch extends existing "kernelcore" option and
>>> introduces kernelcore=reliable option. By specifying
>>> "reliable" instead of specifying the amount of memory,
>>> non-reliable region will be arranged into ZONE_MOVABLE.
>>>
>>> Earlier discussion is at:
>>> https://lkml.org/lkml/2015/10/9/24
>>>
>>
>> Hi Taku,
>>
>> If user don't want to waste a lot of memory, and he only set
>> a few memory to mirrored memory, then the kernelcore is very
>> small, right? That means OS will have a very small normal zone
>> and a very large movable zone.
>
> Right.
>
>> Kernel allocation could only use the unmovable zone. As the
>> normal zone is very small, the kernel allocation maybe OOM,
>> right?
>
> Right.
>
>> Do you mean that we will reuse the movable zone in short-term
>> solution and create a new zone(mirrored zone) in future?
>
> If there is that kind of requirements, I don't oppose
> creating a new zone.
>
As far as I know, some apps(e.g. date base) maybe could only use
the normal zone.
Thanks,
Xishi Qiu
> Sincerely,
> Taku Izumi
>
> .
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-10-20 1:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 13:32 Taku Izumi
2015-10-19 2:25 ` Xishi Qiu
2015-10-20 0:34 ` Izumi, Taku
2015-10-20 1:42 ` Xishi Qiu [this message]
2015-10-21 18:17 ` Luck, Tony
2015-10-22 10:02 ` Kamezawa Hiroyuki
2015-10-22 23:26 ` Luck, Tony
2015-10-23 1:01 ` Izumi, Taku
2015-10-23 1:44 ` Luck, Tony
2015-10-30 6:19 ` Kamezawa Hiroyuki
2015-10-30 19:42 ` Luck, Tony
2015-11-04 6:56 ` Kamezawa Hiroyuki
2015-10-23 3:36 ` Xishi Qiu
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=56259BFF.1090203@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matt@codeblueprint.co.uk \
--cc=mel@csn.ul.ie \
--cc=tony.luck@intel.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