blob: 443f4b44ad97cddc2d8b645c29a55ff88573f864 [file] [log] [blame]
Yasunori Goto6867c932007-08-10 13:00:59 -07001==============
2Memory Hotplug
3==============
4
Yasunori Goto10020ca2007-10-21 16:41:36 -07005Created: Jul 28 2007
6Add description of notifier of memory hotplug Oct 11 2007
Yasunori Goto6867c932007-08-10 13:00:59 -07007
8This document is about memory hotplug including how-to-use and current status.
9Because Memory Hotplug is still under development, contents of this text will
10be changed often.
11
121. Introduction
13 1.1 purpose of memory hotplug
14 1.2. Phases of memory hotplug
15 1.3. Unit of Memory online/offline operation
162. Kernel Configuration
173. sysfs files for memory hotplug
184. Physical memory hot-add phase
19 4.1 Hardware(Firmware) Support
20 4.2 Notify memory hot-add event by hand
215. Logical Memory hot-add phase
22 5.1. State of memory
23 5.2. How to online memory
246. Logical memory remove
25 6.1 Memory offline and ZONE_MOVABLE
26 6.2. How to offline memory
277. Physical memory remove
Yasunori Goto10020ca2007-10-21 16:41:36 -0700288. Memory hotplug event notifier
299. Future Work List
Yasunori Goto6867c932007-08-10 13:00:59 -070030
31Note(1): x86_64's has special implementation for memory hotplug.
32 This text does not describe it.
33Note(2): This text assumes that sysfs is mounted at /sys.
34
35
36---------------
371. Introduction
38---------------
39
401.1 purpose of memory hotplug
41------------
42Memory Hotplug allows users to increase/decrease the amount of memory.
43Generally, there are two purposes.
44
45(A) For changing the amount of memory.
46 This is to allow a feature like capacity on demand.
47(B) For installing/removing DIMMs or NUMA-nodes physically.
48 This is to exchange DIMMs/NUMA-nodes, reduce power consumption, etc.
49
50(A) is required by highly virtualized environments and (B) is required by
51hardware which supports memory power management.
52
53Linux memory hotplug is designed for both purpose.
54
55
561.2. Phases of memory hotplug
57---------------
58There are 2 phases in Memory Hotplug.
59 1) Physical Memory Hotplug phase
60 2) Logical Memory Hotplug phase.
61
62The First phase is to communicate hardware/firmware and make/erase
63environment for hotplugged memory. Basically, this phase is necessary
64for the purpose (B), but this is good phase for communication between
65highly virtualized environments too.
66
67When memory is hotplugged, the kernel recognizes new memory, makes new memory
68management tables, and makes sysfs files for new memory's operation.
69
70If firmware supports notification of connection of new memory to OS,
71this phase is triggered automatically. ACPI can notify this event. If not,
72"probe" operation by system administration is used instead.
73(see Section 4.).
74
75Logical Memory Hotplug phase is to change memory state into
Matt LaPlante19f59462009-04-27 15:06:31 +020076available/unavailable for users. Amount of memory from user's view is
Yasunori Goto6867c932007-08-10 13:00:59 -070077changed by this phase. The kernel makes all memory in it as free pages
78when a memory range is available.
79
80In this document, this phase is described as online/offline.
81
Matt LaPlante19f59462009-04-27 15:06:31 +020082Logical Memory Hotplug phase is triggered by write of sysfs file by system
Yasunori Goto6867c932007-08-10 13:00:59 -070083administrator. For the hot-add case, it must be executed after Physical Hotplug
84phase by hand.
85(However, if you writes udev's hotplug scripts for memory hotplug, these
86 phases can be execute in seamless way.)
87
88
891.3. Unit of Memory online/offline operation
90------------
Li Zhong56a3c652014-06-04 16:07:03 -070091Memory hotplug uses SPARSEMEM memory model which allows memory to be divided
92into chunks of the same size. These chunks are called "sections". The size of
93a memory section is architecture dependent. For example, power uses 16MiB, ia64
94uses 1GiB.
Yasunori Goto6867c932007-08-10 13:00:59 -070095
Li Zhong56a3c652014-06-04 16:07:03 -070096Memory sections are combined into chunks referred to as "memory blocks". The
97size of a memory block is architecture dependent and represents the logical
98unit upon which memory online/offline operations are to be performed. The
99default size of a memory block is the same as memory section size unless an
100architecture specifies otherwise. (see Section 3.)
101
102To determine the size (in bytes) of a memory block please read this file:
Yasunori Goto6867c932007-08-10 13:00:59 -0700103
104/sys/devices/system/memory/block_size_bytes
105
Yasunori Goto6867c932007-08-10 13:00:59 -0700106
107-----------------------
1082. Kernel Configuration
109-----------------------
110To use memory hotplug feature, kernel must be compiled with following
111config options.
112
113- For all memory hotplug
114 Memory model -> Sparse Memory (CONFIG_SPARSEMEM)
115 Allow for memory hot-add (CONFIG_MEMORY_HOTPLUG)
116
117- To enable memory removal, the followings are also necessary
118 Allow for memory hot remove (CONFIG_MEMORY_HOTREMOVE)
119 Page Migration (CONFIG_MIGRATION)
120
121- For ACPI memory hotplug, the followings are also necessary
122 Memory hotplug (under ACPI Support menu) (CONFIG_ACPI_HOTPLUG_MEMORY)
123 This option can be kernel module.
124
125- As a related configuration, if your box has a feature of NUMA-node hotplug
126 via ACPI, then this option is necessary too.
127 ACPI0004,PNP0A05 and PNP0A06 Container Driver (under ACPI Support menu)
128 (CONFIG_ACPI_CONTAINER).
129 This option can be kernel module too.
130
Li Zhong56a3c652014-06-04 16:07:03 -0700131
Yasunori Goto6867c932007-08-10 13:00:59 -0700132--------------------------------
Li Zhong56a3c652014-06-04 16:07:03 -07001333 sysfs files for memory hotplug
Yasunori Goto6867c932007-08-10 13:00:59 -0700134--------------------------------
Li Zhong56a3c652014-06-04 16:07:03 -0700135All memory blocks have their device information in sysfs. Each memory block
136is described under /sys/devices/system/memory as
Yasunori Goto6867c932007-08-10 13:00:59 -0700137
138/sys/devices/system/memory/memoryXXX
Li Zhong56a3c652014-06-04 16:07:03 -0700139(XXX is the memory block id.)
Yasunori Goto6867c932007-08-10 13:00:59 -0700140
Li Zhong56a3c652014-06-04 16:07:03 -0700141For the memory block covered by the sysfs directory. It is expected that all
Nathan Fontenot0c2c99b2011-01-20 10:43:34 -0600142memory sections in this range are present and no memory holes exist in the
143range. Currently there is no way to determine if there is a memory hole, but
144the existence of one should not affect the hotplug capabilities of the memory
145block.
Yasunori Goto6867c932007-08-10 13:00:59 -0700146
Li Zhong56a3c652014-06-04 16:07:03 -0700147For example, assume 1GiB memory block size. A device for a memory starting at
Yasunori Goto6867c932007-08-10 13:00:59 -07001480x100000000 is /sys/device/system/memory/memory4
149(0x100000000 / 1Gib = 4)
150This device covers address range [0x100000000 ... 0x140000000)
151
Sheng Yong82433382015-03-02 02:20:45 +0000152Under each memory block, you can see 5 files:
Yasunori Goto6867c932007-08-10 13:00:59 -0700153
Li Zhong56a3c652014-06-04 16:07:03 -0700154/sys/devices/system/memory/memoryXXX/phys_index
Yasunori Goto6867c932007-08-10 13:00:59 -0700155/sys/devices/system/memory/memoryXXX/phys_device
156/sys/devices/system/memory/memoryXXX/state
Gary Hadec04fc582009-01-06 14:39:14 -0800157/sys/devices/system/memory/memoryXXX/removable
Zhang Zhened2f2402014-10-09 15:26:31 -0700158/sys/devices/system/memory/memoryXXX/valid_zones
Yasunori Goto6867c932007-08-10 13:00:59 -0700159
Li Zhong56a3c652014-06-04 16:07:03 -0700160'phys_index' : read-only and contains memory block id, same as XXX.
Nathan Fontenot0c2c99b2011-01-20 10:43:34 -0600161'state' : read-write
162 at read: contains online/offline state of memory.
Lai Jiangshan511c2ab2012-12-11 16:03:16 -0800163 at write: user can specify "online_kernel",
164 "online_movable", "online", "offline" command
Xishi Qiu59e68a12013-08-22 17:42:44 +0800165 which will be performed on all sections in the block.
Nathan Fontenot0c2c99b2011-01-20 10:43:34 -0600166'phys_device' : read-only: designed to show the name of physical memory
167 device. This is not well implemented now.
168'removable' : read-only: contains an integer value indicating
169 whether the memory block is removable or not
170 removable. A value of 1 indicates that the memory
171 block is removable and a value of 0 indicates that
172 it is not removable. A memory block is removable only if
173 every section in the block is removable.
Zhang Zhened2f2402014-10-09 15:26:31 -0700174'valid_zones' : read-only: designed to show which zones this memory block
175 can be onlined to.
176 The first column shows it's default zone.
177 "memory6/valid_zones: Normal Movable" shows this memoryblock
178 can be onlined to ZONE_NORMAL by default and to ZONE_MOVABLE
179 by online_movable.
180 "memory7/valid_zones: Movable Normal" shows this memoryblock
181 can be onlined to ZONE_MOVABLE by default and to ZONE_NORMAL
182 by online_kernel.
Yasunori Goto6867c932007-08-10 13:00:59 -0700183
184NOTE:
185 These directories/files appear after physical memory hotplug phase.
186
Alex Chiangdee5d0d2009-12-14 17:59:05 -0800187If CONFIG_NUMA is enabled the memoryXXX/ directories can also be accessed
188via symbolic links located in the /sys/devices/system/node/node* directories.
189
190For example:
Gary Hadec04fc582009-01-06 14:39:14 -0800191/sys/devices/system/node/node0/memory9 -> ../../memory/memory9
Yasunori Goto6867c932007-08-10 13:00:59 -0700192
Alex Chiangdee5d0d2009-12-14 17:59:05 -0800193A backlink will also be created:
194/sys/devices/system/memory/memory9/node0 -> ../../node/node0
195
Li Zhong56a3c652014-06-04 16:07:03 -0700196
Yasunori Goto6867c932007-08-10 13:00:59 -0700197--------------------------------
1984. Physical memory hot-add phase
199--------------------------------
200
2014.1 Hardware(Firmware) Support
202------------
203On x86_64/ia64 platform, memory hotplug by ACPI is supported.
204
205In general, the firmware (ACPI) which supports memory hotplug defines
206memory class object of _HID "PNP0C80". When a notify is asserted to PNP0C80,
207Linux's ACPI handler does hot-add memory to the system and calls a hotplug udev
208script. This will be done automatically.
209
210But scripts for memory hotplug are not contained in generic udev package(now).
211You may have to write it by yourself or online/offline memory by hand.
212Please see "How to online memory", "How to offline memory" in this text.
213
214If firmware supports NUMA-node hotplug, and defines an object _HID "ACPI0004",
215"PNP0A05", or "PNP0A06", notification is asserted to it, and ACPI handler
216calls hotplug code for all of objects which are defined in it.
217If memory device is found, memory hotplug code will be called.
218
219
2204.2 Notify memory hot-add event by hand
221------------
David Rientjes7cdb0d22014-06-23 13:22:03 -0700222On some architectures, the firmware may not notify the kernel of a memory
223hotplug event. Therefore, the memory "probe" interface is supported to
224explicitly notify the kernel. This interface depends on
225CONFIG_ARCH_MEMORY_PROBE and can be configured on powerpc, sh, and x86
226if hotplug is supported, although for x86 this should be handled by ACPI
227notification.
Yasunori Goto6867c932007-08-10 13:00:59 -0700228
229Probe interface is located at
230/sys/devices/system/memory/probe
231
232You can tell the physical address of new memory to the kernel by
233
234% echo start_address_of_new_memory > /sys/devices/system/memory/probe
235
Li Zhong56a3c652014-06-04 16:07:03 -0700236Then, [start_address_of_new_memory, start_address_of_new_memory +
237memory_block_size] memory range is hot-added. In this case, hotplug script is
238not called (in current implementation). You'll have to online memory by
239yourself. Please see "How to online memory" in this text.
Yasunori Goto6867c932007-08-10 13:00:59 -0700240
241
242------------------------------
2435. Logical Memory hot-add phase
244------------------------------
245
2465.1. State of memory
247------------
Li Zhong56a3c652014-06-04 16:07:03 -0700248To see (online/offline) state of a memory block, read 'state' file.
Yasunori Goto6867c932007-08-10 13:00:59 -0700249
250% cat /sys/device/system/memory/memoryXXX/state
251
252
Li Zhong56a3c652014-06-04 16:07:03 -0700253If the memory block is online, you'll read "online".
254If the memory block is offline, you'll read "offline".
Yasunori Goto6867c932007-08-10 13:00:59 -0700255
256
2575.2. How to online memory
258------------
Vitaly Kuznetsov31bc3852016-03-15 14:56:48 -0700259When the memory is hot-added, the kernel decides whether or not to "online"
260it according to the policy which can be read from "auto_online_blocks" file:
Yasunori Goto6867c932007-08-10 13:00:59 -0700261
Vitaly Kuznetsov31bc3852016-03-15 14:56:48 -0700262% cat /sys/devices/system/memory/auto_online_blocks
263
264The default is "offline" which means the newly added memory is not in a
265ready-to-use state and you have to "online" the newly added memory blocks
266manually. Automatic onlining can be requested by writing "online" to
267"auto_online_blocks" file:
268
269% echo online > /sys/devices/system/memory/auto_online_blocks
270
271This sets a global policy and impacts all memory blocks that will subsequently
272be hotplugged. Currently offline blocks keep their state. It is possible, under
273certain circumstances, that some memory blocks will be added but will fail to
274online. User space tools can check their "state" files
275(/sys/devices/system/memory/memoryXXX/state) and try to online them manually.
276
277If the automatic onlining wasn't requested, failed, or some memory block was
278offlined it is possible to change the individual block's state by writing to the
279"state" file:
Yasunori Goto6867c932007-08-10 13:00:59 -0700280
281% echo online > /sys/devices/system/memory/memoryXXX/state
282
Li Zhong56a3c652014-06-04 16:07:03 -0700283This onlining will not change the ZONE type of the target memory block,
284If the memory block is in ZONE_NORMAL, you can change it to ZONE_MOVABLE:
Lai Jiangshan511c2ab2012-12-11 16:03:16 -0800285
286% echo online_movable > /sys/devices/system/memory/memoryXXX/state
Li Zhong56a3c652014-06-04 16:07:03 -0700287(NOTE: current limit: this memory block must be adjacent to ZONE_MOVABLE)
Lai Jiangshan511c2ab2012-12-11 16:03:16 -0800288
Li Zhong56a3c652014-06-04 16:07:03 -0700289And if the memory block is in ZONE_MOVABLE, you can change it to ZONE_NORMAL:
Lai Jiangshan511c2ab2012-12-11 16:03:16 -0800290
291% echo online_kernel > /sys/devices/system/memory/memoryXXX/state
Li Zhong56a3c652014-06-04 16:07:03 -0700292(NOTE: current limit: this memory block must be adjacent to ZONE_NORMAL)
Lai Jiangshan511c2ab2012-12-11 16:03:16 -0800293
Li Zhong56a3c652014-06-04 16:07:03 -0700294After this, memory block XXX's state will be 'online' and the amount of
Yasunori Goto6867c932007-08-10 13:00:59 -0700295available memory will be increased.
296
297Currently, newly added memory is added as ZONE_NORMAL (for powerpc, ZONE_DMA).
298This may be changed in future.
299
300
301
302------------------------
3036. Logical memory remove
304------------------------
305
3066.1 Memory offline and ZONE_MOVABLE
307------------
308Memory offlining is more complicated than memory online. Because memory offline
Li Zhong56a3c652014-06-04 16:07:03 -0700309has to make the whole memory block be unused, memory offline can fail if
310the memory block includes memory which cannot be freed.
Yasunori Goto6867c932007-08-10 13:00:59 -0700311
312In general, memory offline can use 2 techniques.
313
Li Zhong56a3c652014-06-04 16:07:03 -0700314(1) reclaim and free all memory in the memory block.
315(2) migrate all pages in the memory block.
Yasunori Goto6867c932007-08-10 13:00:59 -0700316
317In the current implementation, Linux's memory offline uses method (2), freeing
Li Zhong56a3c652014-06-04 16:07:03 -0700318all pages in the memory block by page migration. But not all pages are
Yasunori Goto6867c932007-08-10 13:00:59 -0700319migratable. Under current Linux, migratable pages are anonymous pages and
Li Zhong56a3c652014-06-04 16:07:03 -0700320page caches. For offlining a memory block by migration, the kernel has to
321guarantee that the memory block contains only migratable pages.
Yasunori Goto6867c932007-08-10 13:00:59 -0700322
Li Zhong56a3c652014-06-04 16:07:03 -0700323Now, a boot option for making a memory block which consists of migratable pages
324is supported. By specifying "kernelcore=" or "movablecore=" boot option, you can
Yasunori Goto6867c932007-08-10 13:00:59 -0700325create ZONE_MOVABLE...a zone which is just used for movable pages.
326(See also Documentation/kernel-parameters.txt)
327
328Assume the system has "TOTAL" amount of memory at boot time, this boot option
329creates ZONE_MOVABLE as following.
330
3311) When kernelcore=YYYY boot option is used,
332 Size of memory not for movable pages (not for offline) is YYYY.
333 Size of memory for movable pages (for offline) is TOTAL-YYYY.
334
3352) When movablecore=ZZZZ boot option is used,
336 Size of memory not for movable pages (not for offline) is TOTAL - ZZZZ.
337 Size of memory for movable pages (for offline) is ZZZZ.
338
339
Li Zhong56a3c652014-06-04 16:07:03 -0700340Note: Unfortunately, there is no information to show which memory block belongs
Yasunori Goto6867c932007-08-10 13:00:59 -0700341to ZONE_MOVABLE. This is TBD.
342
343
3446.2. How to offline memory
345------------
Li Zhong56a3c652014-06-04 16:07:03 -0700346You can offline a memory block by using the same sysfs interface that was used
347in memory onlining.
Yasunori Goto6867c932007-08-10 13:00:59 -0700348
349% echo offline > /sys/devices/system/memory/memoryXXX/state
350
Li Zhong56a3c652014-06-04 16:07:03 -0700351If offline succeeds, the state of the memory block is changed to be "offline".
Yasunori Goto6867c932007-08-10 13:00:59 -0700352If it fails, some error core (like -EBUSY) will be returned by the kernel.
Li Zhong56a3c652014-06-04 16:07:03 -0700353Even if a memory block does not belong to ZONE_MOVABLE, you can try to offline
354it. If it doesn't contain 'unmovable' memory, you'll get success.
Yasunori Goto6867c932007-08-10 13:00:59 -0700355
Li Zhong56a3c652014-06-04 16:07:03 -0700356A memory block under ZONE_MOVABLE is considered to be able to be offlined
357easily. But under some busy state, it may return -EBUSY. Even if a memory
358block cannot be offlined due to -EBUSY, you can retry offlining it and may be
359able to offline it (or not). (For example, a page is referred to by some kernel
360internal call and released soon.)
Yasunori Goto6867c932007-08-10 13:00:59 -0700361
362Consideration:
363Memory hotplug's design direction is to make the possibility of memory offlining
364higher and to guarantee unplugging memory under any situation. But it needs
365more work. Returning -EBUSY under some situation may be good because the user
366can decide to retry more or not by himself. Currently, memory offlining code
367does some amount of retry with 120 seconds timeout.
368
369-------------------------
3707. Physical memory remove
371-------------------------
372Need more implementation yet....
373 - Notification completion of remove works by OS to firmware.
374 - Guard from remove if not yet.
375
Yasunori Goto10020ca2007-10-21 16:41:36 -0700376--------------------------------
3778. Memory hotplug event notifier
378--------------------------------
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100379Hotplugging events are sent to a notification queue.
Yasunori Goto10020ca2007-10-21 16:41:36 -0700380
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100381There are six types of notification defined in include/linux/memory.h:
382
383MEM_GOING_ONLINE
Yasunori Goto10020ca2007-10-21 16:41:36 -0700384 Generated before new memory becomes available in order to be able to
385 prepare subsystems to handle memory. The page allocator is still unable
386 to allocate from the new memory.
387
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100388MEM_CANCEL_ONLINE
Yasunori Goto10020ca2007-10-21 16:41:36 -0700389 Generated if MEMORY_GOING_ONLINE fails.
390
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100391MEM_ONLINE
Matt LaPlante19f59462009-04-27 15:06:31 +0200392 Generated when memory has successfully brought online. The callback may
Yasunori Goto10020ca2007-10-21 16:41:36 -0700393 allocate pages from the new memory.
394
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100395MEM_GOING_OFFLINE
Yasunori Goto10020ca2007-10-21 16:41:36 -0700396 Generated to begin the process of offlining memory. Allocations are no
397 longer possible from the memory but some of the memory to be offlined
398 is still in use. The callback can be used to free memory known to a
Li Zhong56a3c652014-06-04 16:07:03 -0700399 subsystem from the indicated memory block.
Yasunori Goto10020ca2007-10-21 16:41:36 -0700400
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100401MEM_CANCEL_OFFLINE
Yasunori Goto10020ca2007-10-21 16:41:36 -0700402 Generated if MEMORY_GOING_OFFLINE fails. Memory is available again from
Li Zhong56a3c652014-06-04 16:07:03 -0700403 the memory block that we attempted to offline.
Yasunori Goto10020ca2007-10-21 16:41:36 -0700404
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100405MEM_OFFLINE
Yasunori Goto10020ca2007-10-21 16:41:36 -0700406 Generated after offlining memory is complete.
407
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100408A callback routine can be registered by calling
409
Yasunori Goto10020ca2007-10-21 16:41:36 -0700410 hotplug_memory_notifier(callback_func, priority)
411
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100412Callback functions with higher values of priority are called before callback
413functions with lower values.
414
415A callback function must have the following prototype:
416
417 int callback_func(
418 struct notifier_block *self, unsigned long action, void *arg);
419
420The first argument of the callback function (self) is a pointer to the block
421of the notifier chain that points to the callback function itself.
422The second argument (action) is one of the event types described above.
423The third argument (arg) passes a pointer of struct memory_notify.
Yasunori Goto10020ca2007-10-21 16:41:36 -0700424
425struct memory_notify {
426 unsigned long start_pfn;
427 unsigned long nr_pages;
Lai Jiangshand9713672012-12-11 16:01:03 -0800428 int status_change_nid_normal;
Lai Jiangshan6715ddf2012-12-12 13:51:49 -0800429 int status_change_nid_high;
Matt LaPlante19f59462009-04-27 15:06:31 +0200430 int status_change_nid;
Yasunori Goto10020ca2007-10-21 16:41:36 -0700431}
432
433start_pfn is start_pfn of online/offline memory.
434nr_pages is # of pages of online/offline memory.
Lai Jiangshand9713672012-12-11 16:01:03 -0800435status_change_nid_normal is set node id when N_NORMAL_MEMORY of nodemask
436is (will be) set/clear, if this is -1, then nodemask status is not changed.
Lai Jiangshan6715ddf2012-12-12 13:51:49 -0800437status_change_nid_high is set node id when N_HIGH_MEMORY of nodemask
438is (will be) set/clear, if this is -1, then nodemask status is not changed.
439status_change_nid is set node id when N_MEMORY of nodemask is (will be)
Yasunori Goto10020ca2007-10-21 16:41:36 -0700440set/clear. It means a new(memoryless) node gets new memory by online and a
441node loses all memory. If this is -1, then nodemask status is not changed.
Lai Jiangshand9713672012-12-11 16:01:03 -0800442If status_changed_nid* >= 0, callback should create/discard structures for the
Yasunori Goto10020ca2007-10-21 16:41:36 -0700443node if necessary.
444
Heinrich Schuchardt433b89c2015-02-22 00:18:49 +0100445The callback routine shall return one of the values
446NOTIFY_DONE, NOTIFY_OK, NOTIFY_BAD, NOTIFY_STOP
447defined in include/linux/notifier.h
448
449NOTIFY_DONE and NOTIFY_OK have no effect on the further processing.
450
451NOTIFY_BAD is used as response to the MEM_GOING_ONLINE, MEM_GOING_OFFLINE,
452MEM_ONLINE, or MEM_OFFLINE action to cancel hotplugging. It stops
453further processing of the notification queue.
454
455NOTIFY_STOP stops further processing of the notification queue.
456
Yasunori Goto6867c932007-08-10 13:00:59 -0700457--------------
Yasunori Goto10020ca2007-10-21 16:41:36 -07004589. Future Work
Yasunori Goto6867c932007-08-10 13:00:59 -0700459--------------
460 - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like
461 sysctl or new control file.
Li Zhong56a3c652014-06-04 16:07:03 -0700462 - showing memory block and physical device relationship.
Yasunori Goto6867c932007-08-10 13:00:59 -0700463 - test and make it better memory offlining.
464 - support HugeTLB page migration and offlining.
465 - memmap removing at memory offline.
466 - physical remove memory.
467