From: Yinghai Lu <yinghai@kernel.org>
To: Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: Linux MM <linux-mm@kvack.org>, wangnan0@huawei.com
Subject: Re: How to boot up an ARM board enabled CONFIG_SPARSEMEM
Date: Tue, 1 Jul 2014 11:45:16 -0700 [thread overview]
Message-ID: <CAE9FiQWpPOELEAOZxxZafpkYqYPurL_Fx_zJsS4XM+DmFCYbxg@mail.gmail.com> (raw)
In-Reply-To: <53B26364.1040606@huawei.com>
On Tue, Jul 1, 2014 at 12:29 AM, Zhang Zhen <zhenzhang.zhang@huawei.com> wrote:
> Hi,
>
> Recently We are testing stable kernel 3.10 on an ARM board.
> It failed to boot if we enabled CONFIG_SPARSEMEM config.
Arm support 2 sockets and numa now?
> 1. In mem_init() and show_mem() compare pfn instead of page just like the patch in attachement.
> 2. Enable CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER when enabled CONFIG_SPARSEMEM.
>
> QUESTION:
>
> I want to know why CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER depends on x86_64 ?
That make memory allocation have less memory hole, from old bootmem bitmap
allocation stage.
Maybe we don't need that anymore as we have memblock allocation that is more
smarter with alignment handling.
Also allocating big size and use them block by block, could save some time on
searching on allocation function when memblock have lots of entries on
memory/reserved arrays.
Thanks
Yinghai
--
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:[~2014-07-01 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53B26229.5030504@huawei.com>
2014-07-01 7:29 ` Zhang Zhen
2014-07-01 18:45 ` Yinghai Lu [this message]
2014-07-02 6:48 ` Zhang Zhen
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=CAE9FiQWpPOELEAOZxxZafpkYqYPurL_Fx_zJsS4XM+DmFCYbxg@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangnan0@huawei.com \
--cc=zhenzhang.zhang@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