Lines Matching refs:of
6 Add description of notifier of memory hotplug Oct 11 2007
9 Because Memory Hotplug is still under development, contents of this text will
13 1.1 purpose of memory hotplug
14 1.2. Phases of memory hotplug
15 1.3. Unit of Memory online/offline operation
22 5.1. State of memory
40 1.1 purpose of memory hotplug
42 Memory Hotplug allows users to increase/decrease the amount of memory.
45 (A) For changing the amount of memory.
56 1.2. Phases of memory hotplug
70 If firmware supports notification of connection of new memory to OS,
76 available/unavailable for users. Amount of memory from user's view is
82 Logical Memory Hotplug phase is triggered by write of sysfs file by system
89 1.3. Unit of Memory online/offline operation
92 into chunks of the same size. These chunks are called "sections". The size of
97 size of a memory block is architecture dependent and represents the logical
99 default size of a memory block is the same as memory section size unless an
102 To determine the size (in bytes) of a memory block please read this file:
125 - As a related configuration, if your box has a feature of NUMA-node hotplug
144 the existence of one should not affect the hotplug capabilities of the memory
162 at read: contains online/offline state of memory.
166 'phys_device' : read-only: designed to show the name of physical memory
170 removable. A value of 1 indicates that the memory
171 block is removable and a value of 0 indicates that
206 memory class object of _HID "PNP0C80". When a notify is asserted to PNP0C80,
216 calls hotplug code for all of objects which are defined in it.
222 On some architectures, the firmware may not notify the kernel of a memory
232 You can tell the physical address of new memory to the kernel by
246 5.1. State of memory
248 To see (online/offline) state of a memory block, read 'state' file.
266 This onlining will not change the ZONE type of the target memory block,
277 After this, memory block XXX's state will be 'online' and the amount of
306 Now, a boot option for making a memory block which consists of migratable pages
311 Assume the system has "TOTAL" amount of memory at boot time, this boot option
315 Size of memory not for movable pages (not for offline) is YYYY.
316 Size of memory for movable pages (for offline) is TOTAL-YYYY.
319 Size of memory not for movable pages (not for offline) is TOTAL - ZZZZ.
320 Size of memory for movable pages (for offline) is ZZZZ.
334 If offline succeeds, the state of the memory block is changed to be "offline".
346 Memory hotplug's design direction is to make the possibility of memory offlining
350 does some amount of retry with 120 seconds timeout.
356 - Notification completion of remove works by OS to firmware.
364 There are six types of notification defined in include/linux/memory.h:
379 Generated to begin the process of offlining memory. Allocations are no
380 longer possible from the memory but some of the memory to be offlined
395 Callback functions with higher values of priority are called before callback
403 The first argument of the callback function (self) is a pointer to the block
404 of the notifier chain that points to the callback function itself.
405 The second argument (action) is one of the event types described above.
406 The third argument (arg) passes a pointer of struct memory_notify.
416 start_pfn is start_pfn of online/offline memory.
417 nr_pages is # of pages of online/offline memory.
418 status_change_nid_normal is set node id when N_NORMAL_MEMORY of nodemask
420 status_change_nid_high is set node id when N_HIGH_MEMORY of nodemask
422 status_change_nid is set node id when N_MEMORY of nodemask is (will be)
428 The callback routine shall return one of the values
436 further processing of the notification queue.
438 NOTIFY_STOP stops further processing of the notification queue.