From: Chen Feng <puck.chen@hisilicon.com>
To: catalin.marinas@arm.com, will.deacon@arm.com,
ard.biesheuvel@linaro.org, mark.rutland@arm.com,
akpm@linux-foundation.org, robin.murphy@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mhocko@suse.com,
kirill.shutemov@linux.intel.com, rientjes@google.com,
linux-mm@kvack.org
Cc: puck.chen@hisilicon.com, puck.chen@foxmail.com,
oliver.fu@hisilicon.com, linuxarm@huawei.com,
dan.zhao@hisilicon.com, suzhuangluan@hisilicon.com,
yudongbin@hislicon.com, albert.lubing@hisilicon.com,
xuyiping@hisilicon.com, saberlily.xia@hisilicon.com
Subject: [PATCH 1/2] arm64: mem-model: add flatmem model for arm64
Date: Tue, 5 Apr 2016 16:22:51 +0800 [thread overview]
Message-ID: <1459844572-53069-1-git-send-email-puck.chen@hisilicon.com> (raw)
We can reduce the memory allocated at mem-map
by flatmem.
currently, the default memory-model in arm64 is
sparse memory. The mem-map array is not freed in
this scene. If the physical address is too long,
it will reserved too much memory for the mem-map
array.
Signed-off-by: Chen Feng <puck.chen@hisilicon.com>
Signed-off-by: Fu Jun <oliver.fu@hisilicon.com>
---
arch/arm64/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 4f43622..c18930d 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -559,6 +559,9 @@ config ARCH_SPARSEMEM_ENABLE
def_bool y
select SPARSEMEM_VMEMMAP_ENABLE
+config ARCH_FLATMEM_ENABLE
+ def_bool y
+
config ARCH_SPARSEMEM_DEFAULT
def_bool ARCH_SPARSEMEM_ENABLE
--
1.9.1
--
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 reply other threads:[~2016-04-05 8:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 8:22 Chen Feng [this message]
2016-04-05 8:22 ` [PATCH 2/2] arm64: mm: make pfn always valid with flat memory Chen Feng
2016-04-07 7:39 ` Chen Feng
2016-04-11 11:08 ` Xishi Qiu
2016-04-12 15:00 ` Catalin Marinas
2016-04-07 7:38 ` [PATCH 1/2] arm64: mem-model: add flatmem model for arm64 Chen Feng
2016-04-07 14:21 ` Will Deacon
2016-04-11 2:49 ` Chen Feng
2016-04-11 7:35 ` Ard Biesheuvel
2016-04-11 7:55 ` Chen Feng
2016-04-11 8:00 ` Ard Biesheuvel
2016-04-11 9:59 ` Chen Feng
2016-04-11 10:31 ` Ard Biesheuvel
2016-04-11 10:40 ` Will Deacon
2016-04-11 10:57 ` Chen Feng
2016-04-11 18:11 ` Laura Abbott
2016-04-12 14:44 ` Catalin Marinas
2016-04-12 14:59 ` Catalin Marinas
2016-04-20 3:18 ` Chen Feng
2016-04-20 9:32 ` Catalin Marinas
2016-04-11 10:48 ` Chen Feng
2016-04-11 11:02 ` Ard Biesheuvel
2016-04-12 14:03 ` Jungseok Lee
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=1459844572-53069-1-git-send-email-puck.chen@hisilicon.com \
--to=puck.chen@hisilicon.com \
--cc=akpm@linux-foundation.org \
--cc=albert.lubing@hisilicon.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dan.zhao@hisilicon.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=oliver.fu@hisilicon.com \
--cc=puck.chen@foxmail.com \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=saberlily.xia@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=xuyiping@hisilicon.com \
--cc=yudongbin@hislicon.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;
as well as URLs for NNTP newsgroup(s).