From: IWAMOTO Toshihiro <iwamoto@valinux.co.jp>
To: linux-kernel@vger.kernel.org, lhms-devel@lists.sourceforge.net
Subject: [patch 0/3] memory hotplug prototype
Date: Tue, 06 Apr 2004 19:53:53 +0900 [thread overview]
Message-ID: <20040406105353.9BDE8705DE@sv1.valinux.co.jp> (raw)
This is an updated version of memory hotplug prototype patch, which I
have posted here several times.
Main changes are:
* Changes to make hotpluggable normal zones possible:
* Added two fields (removable, enabled) to pglist_data.
* Added __GFP_HOTREMOVABLE macro for page caches and
anonymous pages.
* Added an element to node_zonelists[].
node_zonelists[3] is for __GFP_HOTREMOVABLE.
* node_zonelists[] are calculated using pgdat->removable and
pgdat->enabled. zone_active[] checks have been removed.
* Remap code has been cleaned up, to share code with hugepage
handling and better readability.
* Some hack to work better under high IO load. (incomplete)
* Changed page remapping rollback detection logic not to use
PG_again bit as suggested by Dave Hansen in
lhms-devel@sourceforge. PG_again is left for consistency
checks. (not tested well)
* Added an argument to remap_onepage() specifying a node to
allocate replacement pages. (NUMA support, incomplete)
/proc/memhotplug interface has been changed. For example:
# echo plug 1 > /proc/memhotplug
Plugs node 1.
# echo enable 1 > /proc/memhotplug
Enables page allocation from node 1.
# echo disable 1 > /proc/memhotplug
Disables page allocation from node 1.
# echo remap 5 > /proc/memhotplug
Free pages in zone 5 by remapping.
# echo unplug 1 > /proc/memhotplug
Unplugs node 1. (All pages must be freed in advance)
$ cat /proc/memhotplug
Node 0 enabled nonhotremovable
DMA[0]: free 250, active 940, present 4096
Normal[1]: free 307, active 101623, present 126976
Node 1 enabled hotremovable
Normal[5]: free 336, active 9287, present 83968
HighMem[6]: free 88, active 14406, present 45056
Known issues/TODO items:
* kswapd doesn't terminate when a node is unplugged.
* Currently, a page is written back to disk before remapping
if it has a dirty buffer. This can be too slow, so
such pages needs to be handled without issueing writebacks.
I guess this would require a new vfs interface.
My patch consists of 3 files:
1. memoryhotplug.patch
The main patch.
2. va-emulation_memhotplug.patch
to emulate hotpluggable memory blocks on usual PC.
3. va-proc_memhotplug.patch
/proc/memhotplug interface.
They are sent as followups to this mail and will be followed by
Takahashi's hugetlbfs page remapping patches shortly.
--
IWAMOTO Toshihiro
next reply other threads:[~2004-04-06 10:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 10:53 IWAMOTO Toshihiro [this message]
2004-04-06 10:56 ` [patch 1/3] memory hotplug prototype IWAMOTO Toshihiro
2004-04-06 17:12 ` Dave Hansen
2004-04-07 6:10 ` IWAMOTO Toshihiro
2004-04-06 10:58 ` [patch 2/3] " IWAMOTO Toshihiro
2004-04-06 10:59 ` [patch 3/3] " IWAMOTO Toshihiro
2004-04-06 11:47 ` [patch 0/3] " IWAMOTO Toshihiro
2004-04-06 12:41 ` [patch 0/6] memory hotplug for hugetlbpages Hirokazu Takahashi
2004-04-06 12:44 ` [patch 1/6] " Hirokazu Takahashi
2004-04-06 12:45 ` [patch 2/6] " Hirokazu Takahashi
2004-04-06 12:45 ` [patch 3/6] " Hirokazu Takahashi
2004-04-06 12:48 ` [Lhms-devel] [patch 4/6] " Hirokazu Takahashi
2004-04-06 13:02 ` Russell King
2004-04-06 13:11 ` Hirokazu Takahashi
2004-04-06 12:49 ` [patch 5/6] " Hirokazu Takahashi
2004-04-06 12:50 ` [patch 6/6] " Hirokazu Takahashi
2004-04-07 18:12 ` [patch 0/3] memory hotplug prototype Martin J. Bligh
2004-04-07 18:59 ` [Lhms-devel] " Mike Kravetz
2004-04-07 19:20 ` Dave Hansen
2004-04-07 22:33 ` Martin J. Bligh
2004-04-08 12:41 ` Hirokazu Takahashi
2004-04-08 9:16 ` IWAMOTO Toshihiro
2004-04-08 10:19 ` [Lhms-devel] " IWAMOTO Toshihiro
2004-04-08 12:10 ` Hirokazu Takahashi
2004-04-08 16:56 ` Martin J. Bligh
2004-04-09 2:37 ` IWAMOTO Toshihiro
2004-04-09 5:18 ` Martin J. Bligh
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=20040406105353.9BDE8705DE@sv1.valinux.co.jp \
--to=iwamoto@valinux.co.jp \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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).