From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org
Cc: rientjes@google.com, liuj97@gmail.com, len.brown@intel.com,
benh@kernel.crashing.org, paulus@samba.org, cl@linux.com,
minchan.kim@gmail.com, akpm@linux-foundation.org,
kosaki.motohiro@jp.fujitsu.com, wency@cn.fujitsu.com
Subject: [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory
Date: Mon, 9 Jul 2012 19:21:22 +0900 [thread overview]
Message-ID: <4FFAB0A2.8070304@jp.fujitsu.com> (raw)
This patch series aims to support physical memory hot-remove.
[RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory
[RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove
[RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug
[RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs
[RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks
[RFC PATCH v3 6/13] memory-hotplug : add memory_block_release
[RFC PATCH v3 7/13] memory-hotplug : remove_memory calls __remove_pages
[RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem
[RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for
sparse-vmemmap
[RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap
[RFC PATCH v3 11/13] memory-hotplug : free memmap of sparse-vmemmap
[RFC PATCH v3 12/13] memory-hotplug : add node_device_release
[RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node
Even if you apply these patches, you cannot remove the physical memory
completely since these patches are still under development. I want you to
cooperate to improve the physical memory hot-remove. So please review these
patches and give your comment/idea.
The patches can free/remove following things:
- acpi_memory_info : [RFC PATCH 2/13]
- /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 4/13]
- iomem_resource : [RFC PATCH 5/13]
- mem_section and related sysfs files : [RFC PATCH 6-11/13]
- node and related sysfs files : [RFC PATCH 12-13/13]
The patches cannot do following things yet:
- page table of removed memory
If you find lack of function for physical memory hot-remove, please let me
know.
change log of v3:
* rebase to 3.5.0-rc6
[RFC PATCH v2 2/13]
* remove extra kobject_put()
* The patch was commented by Wen. Wen's comment is
"acpi_memory_device_remove() should ignore a return value of
remove_memory() since caller does not care the return value".
But I did not change it since I think caller should care the
return value. And I am trying to fix it as follow:
https://lkml.org/lkml/2012/7/5/624
[RFC PATCH v2 4/13]
* remove a firmware_memmap_entry allocated by kzmalloc()
change log of v2:
[RFC PATCH v2 2/13]
* check whether memory block is offline or not before calling offline_memory()
* check whether section is valid or not in is_memblk_offline()
* call kobject_put() for each memory_block in is_memblk_offline()
[RFC PATCH v2 3/13]
* unify the end argument of firmware_map_add_early/hotplug
[RFC PATCH v2 4/13]
* add release_firmware_map_entry() for freeing firmware_map_entry
[RFC PATCH v2 6/13]
* add release_memory_block() for freeing memory_block
[RFC PATCH v2 11/13]
* fix wrong arguments of free_pages()
---
arch/powerpc/platforms/pseries/hotplug-memory.c | 16 +-
arch/x86/mm/init_64.c | 144 ++++++++++++++++++++++++
drivers/acpi/acpi_memhotplug.c | 28 ++++
drivers/base/memory.c | 54 ++++++++-
drivers/base/node.c | 7 +
drivers/firmware/memmap.c | 78 ++++++++++++-
include/linux/firmware-map.h | 6 +
include/linux/memory.h | 5
include/linux/memory_hotplug.h | 17 --
include/linux/mm.h | 5
mm/memory_hotplug.c | 98 ++++++++++++----
mm/sparse.c | 5
12 files changed, 414 insertions(+), 49 deletions(-)
--
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-07-09 10:21 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 10:21 Yasuaki Ishimatsu [this message]
2012-07-09 10:23 ` [RFC PATCH v3 1/13] memory-hotplug : rename remove_memory to offline_memory Yasuaki Ishimatsu
2012-07-09 10:24 ` [RFC PATCH v3 2/13] memory-hotplug : add physical memory hotplug code to acpi_memory_device_remove Yasuaki Ishimatsu
2012-07-13 3:26 ` Wen Congyang
2012-07-17 0:46 ` Yasuaki Ishimatsu
2012-07-13 3:35 ` Wen Congyang
2012-07-17 1:44 ` Yasuaki Ishimatsu
2012-07-17 1:54 ` Yasuaki Ishimatsu
2012-07-17 2:32 ` Wen Congyang
2012-07-17 3:08 ` Yasuaki Ishimatsu
2012-07-17 3:32 ` Wen Congyang
2012-07-17 4:51 ` Yasuaki Ishimatsu
2012-07-17 5:17 ` Wen Congyang
2012-07-17 5:19 ` Yasuaki Ishimatsu
2012-07-13 10:40 ` Wen Congyang
2012-07-17 1:10 ` Yasuaki Ishimatsu
2012-07-09 10:25 ` [RFC PATCH v3 3/13] memory-hotplug : unify argument of firmware_map_add_early/hotplug Yasuaki Ishimatsu
2012-07-11 15:30 ` Dave Hansen
2012-07-12 4:52 ` Yasuaki Ishimatsu
2012-07-12 13:40 ` Dave Hansen
2012-07-13 4:34 ` Yasuaki Ishimatsu
2012-07-13 5:11 ` Yasuaki Ishimatsu
2012-07-09 10:26 ` [RFC PATCH v3 4/13] memory-hotplug : remove /sys/firmware/memmap/X sysfs Yasuaki Ishimatsu
2012-07-13 9:10 ` Wen Congyang
2012-07-17 0:28 ` Yasuaki Ishimatsu
2012-07-16 2:32 ` Wen Congyang
2012-07-17 0:30 ` Yasuaki Ishimatsu
2012-07-09 10:26 ` [RFC PATCH v3 5/13] memory-hotplug : does not release memory region in PAGES_PER_SECTION chunks Yasuaki Ishimatsu
2012-07-13 3:42 ` Wen Congyang
2012-07-09 10:27 ` [RFC PATCH v3 6/13] memory-hotplug : add memory_block_release Yasuaki Ishimatsu
2012-07-09 10:28 ` [RFC PATCH v3 7/13] memory-hotplug : remove_memory calls __remove_pages Yasuaki Ishimatsu
2012-07-09 10:29 ` [RFC PATCH v3 8/13] memory-hotplug : check page type in get_page_bootmem Yasuaki Ishimatsu
2012-07-09 10:30 ` [RFC PATCH v3 9/13] memory-hotplug : move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap Yasuaki Ishimatsu
2012-07-09 10:32 ` [RFC PATCH v3 10/13] memory-hotplug : implement register_page_bootmem_info_section of sparse-vmemmap Yasuaki Ishimatsu
2012-07-09 10:33 ` [RFC PATCH v3 11/13] memory-hotplug : free memmap " Yasuaki Ishimatsu
2012-07-11 5:06 ` Wen Congyang
2012-07-11 5:52 ` Yasuaki Ishimatsu
2012-07-11 6:25 ` Wen Congyang
2012-07-11 6:48 ` Yasuaki Ishimatsu
2012-07-11 7:27 ` Wen Congyang
2012-07-09 10:34 ` [RFC PATCH v3 12/13] memory-hotplug : add node_device_release Yasuaki Ishimatsu
2012-07-09 10:35 ` [RFC PATCH v3 13/13] memory-hotplug : remove sysfs file of node Yasuaki Ishimatsu
2012-07-09 15:18 ` [RFC PATCH v3 0/13] memory-hotplug : hot-remove physical memory Christoph Lameter
2012-07-10 9:58 ` Yasuaki Ishimatsu
2012-07-10 16:50 ` Jiang Liu
2012-07-11 0:09 ` Yasuaki Ishimatsu
2012-07-11 0:21 ` Jiang Liu
2012-07-11 0:54 ` Yasuaki Ishimatsu
2012-07-11 14:24 ` Jiang Liu
2012-07-11 1:52 ` Wen Congyang
2012-07-11 2:24 ` 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=4FFAB0A2.8070304@jp.fujitsu.com \
--to=isimatu.yasuaki@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liuj97@gmail.com \
--cc=minchan.kim@gmail.com \
--cc=paulus@samba.org \
--cc=rientjes@google.com \
--cc=wency@cn.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