From: Xishi Qiu <qiuxishi@huawei.com>
To: Tony Luck <tony.luck@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
Xiexiuqi <xiexiuqi@huawei.com>
Subject: Re: [RFC 0/3] Mirrored memory support for boot time allocations
Date: Mon, 18 May 2015 16:23:23 +0800 [thread overview]
Message-ID: <5559A17B.90401@huawei.com> (raw)
In-Reply-To: <55599BAA.20204@huawei.com>
Add linux-mm@kvack.org
On 2015/5/18 15:58, Xishi Qiu wrote:
> On 2015/2/7 5:54, Tony Luck wrote:
>
>> Platforms that support a mix of mirrored and regular memory are coming.
>>
>> We'd like to use the mirrored memory for kernel code, data and dynamically
>> allocated data because our machine check recovery code cannot fix problems
>> there. This series modifies the memblock allocator to comprehend mirrored
>> memory and use it for all boot time allocations. Later I'll dig into page_alloc.c
>> to put the leftover mirrored memory into a zone to be used for kernel allocation
>> by slab/slob/slub and others.
>
> Hi Tony,
>
> Is it means that you will create a new zone to fill mirrored memory, like the
> movable zone, right?
> I think this will change a lot of code, why not create a new migrate type?
> such as CMA, e.g. MIGRATE_MIRROR
>
> Thanks,
> Xishi Qiu
>
>>
>> You'll see why this is just RFC when you get to part 3.
>>
>> Tony Luck (3):
>> mm/memblock: Add extra "flag" to memblock to allow selection of memory
>> based on attribute
>> mm/memblock: Allocate boot time data structures from mirrored memory
>> x86, mirror: x86 enabling - find mirrored memory ranges and tell
>> memblock
>>
>> arch/s390/kernel/crash_dump.c | 4 +-
>> arch/sparc/mm/init_64.c | 4 +-
>> arch/x86/kernel/check.c | 2 +-
>> arch/x86/kernel/e820.c | 2 +-
>> arch/x86/mm/init_32.c | 2 +-
>> arch/x86/mm/memtest.c | 2 +-
>> include/linux/memblock.h | 43 ++++++++++------
>> mm/cma.c | 4 +-
>> mm/memblock.c | 113 ++++++++++++++++++++++++++++++++----------
>> mm/nobootmem.c | 12 ++++-
>> 10 files changed, 135 insertions(+), 53 deletions(-)
>>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> .
>
--
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-05-18 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1423259664.git.tony.luck@intel.com>
2015-02-06 22:28 ` Tony Luck
[not found] ` <7bdbb1a569d487b3a772fbb7b66b9498d6cee551.1423259664.git.tony.luck@intel.com>
[not found] ` <55599E2F.4060800@huawei.com>
2015-05-18 17:36 ` [RFC 3/3] x86, mirror: x86 enabling - find mirrored memory ranges and tell memblock Luck, Tony
[not found] ` <55599BAA.20204@huawei.com>
2015-05-18 8:23 ` Xishi Qiu [this message]
2015-05-18 17:42 ` [RFC 0/3] Mirrored memory support for boot time allocations Luck, Tony
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=5559A17B.90401@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tony.luck@intel.com \
--cc=xiexiuqi@huawei.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