[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1353335246-9127-1-git-send-email-tangchen@cn.fujitsu.com>
Date: Mon, 19 Nov 2012 22:27:21 +0800
From: Tang Chen <tangchen@...fujitsu.com>
To: tangchen@...fujitsu.com, wency@...fujitsu.com,
linfeng@...fujitsu.com, rob@...dley.net, akpm@...ux-foundation.org,
isimatu.yasuaki@...fujitsu.com, laijs@...fujitsu.com,
jiang.liu@...wei.com, kosaki.motohiro@...fujitsu.com,
minchan.kim@...il.com, mgorman@...e.de, rientjes@...gle.com,
yinghai@...nel.org, rusty@...tcorp.com.au
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-doc@...r.kernel.org
Subject: [PATCH 0/5] Add movablecore_map boot option.
This patchset provide a boot option for user to specify ZONE_MOVABLE memory
map for each node in the system.
movablecore_map=nn[KMG]@ss[KMG]
This option make sure memory range from ss to ss+nn is movable memory.
1) If the range is involved in a single node, then from ss to the end of
the node will be ZONE_MOVABLE.
2) If the range covers two or more nodes, then from ss to the end of
the node will be ZONE_MOVABLE, and all the other nodes will only
have ZONE_MOVABLE.
3) If no range is in the node, then the node will have no ZONE_MOVABLE
unless kernelcore or movablecore is specified.
4) This option could be specified at most MAX_NUMNODES times.
5) If kernelcore or movablecore is also specified, movablecore_map will have
higher priority to be satisfied.
6) This option has no conflict with memmap option.
Tang Chen (4):
page_alloc: add movable_memmap kernel parameter
page_alloc: Sanitize movablecore_map.
page_alloc: Limit movable zone areas with movablecore_map parameter
page_alloc: Bootmem limit with movablecore_map
Yasuaki Ishimatsu (1):
x86: get pg_data_t's memory from other node
Documentation/kernel-parameters.txt | 17 +++
arch/x86/mm/numa.c | 9 +-
include/linux/memblock.h | 1 +
include/linux/mm.h | 11 ++
mm/memblock.c | 43 ++++++-
mm/page_alloc.c | 233 ++++++++++++++++++++++++++++++++++-
6 files changed, 307 insertions(+), 7 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists