Lines Matching refs:memory
12 There are six types of notification defined in ``include/linux/memory.h``:
15 Generated before new memory becomes available in order to be able to
16 prepare subsystems to handle memory. The page allocator is still unable
17 to allocate from the new memory.
23 Generated when memory has successfully brought online. The callback may
24 allocate pages from the new memory.
27 Generated to begin the process of offlining memory. Allocations are no
28 longer possible from the memory but some of the memory to be offlined
29 is still in use. The callback can be used to free memory known to a
30 subsystem from the indicated memory block.
34 the memory block that we attempted to offline.
37 Generated after offlining memory is complete.
63 - start_pfn is start_pfn of online/offline memory.
64 - nr_pages is # of pages of online/offline memory.
68 set/clear. It means a new(memoryless) node gets new memory by online and a
69 node loses all memory. If this is -1, then nodemask status is not changed.
89 When adding/removing memory that uses memory block devices (i.e. ordinary RAM),
92 - synchronize against online/offline requests (e.g. via sysfs). This way, memory
94 space once memory has been fully added. And when removing memory, we
99 device_hotplug_lock when adding memory and user space tries to online that
100 memory faster than expected:
110 onlining/offlining of memory should be done via device_online()/
114 When adding/removing/onlining/offlining memory or adding/removing
115 heterogeneous/device memory, we should always hold the mem_hotplug_lock in
116 write mode to serialise memory hotplug (e.g. access to global/zone
121 implementation, so code accessing memory can protect from that memory