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: [PART1 Patch 0/3] mm, memory-hotplug: allow to online movable memory
Date: Wed, 31 Oct 2012 13:40:33 +0800 [thread overview]
Message-ID: <1351662036-7435-1-git-send-email-wency@cn.fujitsu.com> (raw)
From: Lai Jiangshan <laijs@cn.fujitsu.com>
This patch is part1 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
Movable memory is a very important concept of memory-management,
we need to consolidate it and make use of it on systems.
Movable memory is needed for
anti-fragmentation(hugepage, big-order allocation...)
logic hot-remove(virtualization, Memory capacity on Demand)
physic hot-remove(power-saving, hardware partitioning, hardware fault management)
All these require dynamic configuring the memory and making better utilities of
memories and safer. We also need physic hot-remove, so we need movable node too.
(Although some systems support physic-memory-migration, we don't require all
memory on physic-node is movable, but movable node is still needed here
for logic-node if we want to make physic-migration is transparent)
We add dynamic configuration commands "online_movalbe" and "online_kernel" in
this patchset, and you can't make a movable node(it will be implemented in
part4).
Usage:
1. online_movable:
echo online_movable >/sys/devices/system/memory/memoryX/state
The memory must be offlined before doing this.
2. online_kernel:
echo online_kernel >/sys/devices/system/memory/memoryX/state
The memory must be offlined before doing this.
3. online:
echo online_kernel >/sys/devices/system/memory/memoryX/state
The memory must be offline before doing this. This operation does't change
the memory's attribute: movable or normal/high
Note:
You only can move the highest memory in normal/high zone to movable zone,
and only can move the lowest memory in movable zone to normal/high zone.
Lai Jiangshan (3):
mm, memory-hotplug: dynamic configure movable memory and portion
memory
memory_hotplug: handle empty zone when online_movable/online_kernel
memory_hotplug: ensure every online node has NORMAL memory
Documentation/memory-hotplug.txt | 14 ++-
drivers/base/memory.c | 27 +++---
include/linux/memory_hotplug.h | 13 ++-
mm/memory_hotplug.c | 180 ++++++++++++++++++++++++++++++++++++++-
4 files changed, 221 insertions(+), 13 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 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 5:40 Wen Congyang [this message]
2012-10-31 5:40 ` [PART1 Patch 1/3] mm, memory-hotplug: dynamic configure movable memory and portion memory Wen Congyang
2012-10-31 5:40 ` [PART1 Patch 2/3] memory_hotplug: handle empty zone when online_movable/online_kernel Wen Congyang
2012-10-31 5:40 ` [PART1 Patch 3/3] memory_hotplug: ensure every online node has NORMAL memory 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=1351662036-7435-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).