From: Wen Congyang <wency@cn.fujitsu.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org
Cc: Rob Landley <rob@landley.net>,
Andrew Morton <akpm@linux-foundation.org>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Jiang Liu <jiang.liu@huawei.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>, Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Yinghai Lu <yinghai@kernel.org>,
"rusty@rustcorp.com.au" <rusty@rustcorp.com.au>
Subject: [PART5 Patch 0/5] introduce a new boot option 'kernelcore_max_addr'
Date: Wed, 31 Oct 2012 17:21:38 +0800 [thread overview]
Message-ID: <1351675303-11786-1-git-send-email-wency@cn.fujitsu.com> (raw)
From: Lai Jiangshan <laijs@cn.fujitsu.com>
This patch is part5 of the following patchset:
https://lkml.org/lkml/2012/10/29/319
The patchset is based on Linus's tree with these three patches already applied:
https://lkml.org/lkml/2012/10/24/151
https://lkml.org/lkml/2012/10/26/150
Part1 is here:
https://lkml.org/lkml/2012/10/31/30
Part2 is here:
http://marc.info/?l=linux-kernel&m=135166705909544&w=2
Part3 is here:
http://marc.info/?l=linux-kernel&m=135167050510527&w=2
Part4 is here:
http://marc.info/?l=linux-kernel&m=135167344211401&w=2
You can apply this patch without the other parts. But it only can work with
part1-5.
We need something like kernelcore_max_addr=XX boot option to limit the
kernelcore upper address.
The memory with higher address will be migratable(movable) and they
are easier to be offline(always ready to be offline when the system don't require
so much memory).
It makes things easy when we dynamic hot-add/remove memory, make better
utilities of memories, and helps for THP.
Lai Jiangshan (1):
page_alloc: add kernelcore_max_addr
Yasuaki Ishimatsu (4):
x86: get pg_data_t's memory from other node
x86: use memblock_set_current_limit() to set memblock.current_limit
memblock: limit memory address from memblock
memblock: compare current_limit with end variable at
memblock_find_in_range_node()
Documentation/kernel-parameters.txt | 9 +++++++++
arch/x86/kernel/setup.c | 4 ++--
arch/x86/mm/numa.c | 8 ++++++--
include/linux/memblock.h | 1 +
mm/memblock.c | 10 +++++++---
mm/page_alloc.c | 33 ++++++++++++++++++++++++++++++++-
6 files changed, 57 insertions(+), 8 deletions(-)
--
1.8.0
--
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:[~2012-10-31 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 9:21 Wen Congyang [this message]
2012-10-31 9:21 ` [PART5 Patch 1/5] page_alloc: add kernelcore_max_addr Wen Congyang
2012-12-19 19:26 ` Randy Dunlap
2012-12-21 1:54 ` Tang Chen
2012-10-31 9:21 ` [PART5 Patch 2/5] x86: get pg_data_t's memory from other node Wen Congyang
2012-10-31 9:21 ` [PART5 Patch 3/5] x86: use memblock_set_current_limit() to set memblock.current_limit Wen Congyang
2012-10-31 9:21 ` [PART5 Patch 4/5] memblock: limit memory address from memblock Wen Congyang
2012-10-31 9:21 ` [PART5 Patch 5/5] memblock: compare current_limit with end variable at memblock_find_in_range_node() Wen Congyang
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=1351675303-11786-1-git-send-email-wency@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=yinghai@kernel.org \
/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).