From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Linux-MM <linux-mm@kvack.org>
Cc: mel@csn.ul.ie, y-goto@jp.fujitsu.com, clameter@sgi.com
Subject: [Patch] memory unplug v3 [0/4]
Date: Tue, 22 May 2007 15:58:24 +0900 [thread overview]
Message-ID: <20070522155824.563f5873.kamezawa.hiroyu@jp.fujitsu.com> (raw)
This is memory unplug base patcheset v3 against 2.6.22-rc1-mm1.
just for review and for testers.
Changelog V2->V3
- Using Meln's page grouping method. this simplifies the whole patch set.
MIGRATE_ISOLATE migratetype is added.
- restructured patch series.
- rebased to 2.6.22-rc1-mm1.
- page is isolated ASAP patch is removed.
- several fixes.
We tested this patch on ia64/NUMA and ia64/SMP.
How to use
- user kernelcore=XXX boot option to create ZONE_MOVABLE.
Memory unplug itself can work without ZONE_MOVABLE but it will be
better to use kernelcore= if your section size is big.
- After bootup, execute following.
# echo "offline" > /sys/devices/system/memory/memoryX/state
- you can push back offlined memory by following
# echo "online" > /sys/devices/system/memory/memoryX/state
TODO
- remove memmap after memory unplug. (for sparsemem)
- more tests and find - page which cannot be freed -
- Now, there is no check around ZONE_MOVABLE and bootmem.
I hope bootmem can treat kernelcore=....
- add better logic to allocate memory for migration.
- speed up under heavy workload.
- node hotplug support
- Should make i386/x86-64/powerpc interface code. But not yet
If you have a request to add interface for test, please tell me.
4 patches are there
[1] page isolation patch
[2] migration by kernel patch
[3] page hot removal patch
[4] ia64 interface patch
Thanks,
-Kame
--
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:[~2007-05-22 6:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 6:58 KAMEZAWA Hiroyuki [this message]
2007-05-22 7:01 ` [Patch] memory unplug v3 [1/4] page isolation KAMEZAWA Hiroyuki
2007-05-22 10:19 ` Mel Gorman
2007-05-22 11:01 ` KAMEZAWA Hiroyuki
2007-05-22 18:38 ` Christoph Lameter
2007-05-23 1:41 ` KAMEZAWA Hiroyuki
2007-05-22 7:04 ` [Patch] memory unplug v3 [2/4] migration by kernel KAMEZAWA Hiroyuki
2007-05-22 18:49 ` Christoph Lameter
2007-05-23 1:45 ` KAMEZAWA Hiroyuki
2007-05-23 1:56 ` Christoph Lameter
2007-05-23 2:09 ` KAMEZAWA Hiroyuki
2007-05-23 19:14 ` Mel Gorman
2007-05-25 7:43 ` KAMEZAWA Hiroyuki
2007-05-22 7:07 ` [Patch] memory unplug v3 [3/4] page removal KAMEZAWA Hiroyuki
2007-05-22 18:52 ` Christoph Lameter
2007-05-23 1:50 ` KAMEZAWA Hiroyuki
2007-05-22 7:08 ` [Patch] memory unplug v3 [4/4] ia64 interface KAMEZAWA Hiroyuki
2007-05-22 18:34 ` [Patch] memory unplug v3 [0/4] Christoph Lameter
2007-05-23 1:59 ` KAMEZAWA Hiroyuki
2007-05-23 2:09 ` Christoph Lameter
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=20070522155824.563f5873.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=y-goto@jp.fujitsu.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