Lines Matching refs:be

10 be changed often.
83 administrator. For the hot-add case, it must be executed after Physical Hotplug
86  phases can be execute in seamless way.)
91 Memory hotplug uses SPARSEMEM memory model which allows memory to be divided
98 unit upon which memory online/offline operations are to be performed. The
110 To use memory hotplug feature, kernel must be compiled with following
123     This option can be kernel module.
129     This option can be kernel module too.
165                     which will be performed on all sections in the block.
175 		    can be onlined to.
178 		    can be onlined to ZONE_NORMAL by default and to ZONE_MOVABLE
181 		    can be onlined to ZONE_MOVABLE by default and to ZONE_NORMAL
187 If CONFIG_NUMA is enabled the memoryXXX/ directories can also be accessed
193 A backlink will also be created:
208 script. This will be done automatically.
217 If memory device is found, memory hotplug code will be called.
225 CONFIG_ARCH_MEMORY_PROBE and can be configured on powerpc, sh, and x86
226 if hotplug is supported, although for x86 this should be handled by ACPI
270 (NOTE: current limit: this memory block must be adjacent to ZONE_MOVABLE)
275 (NOTE: current limit: this memory block must be adjacent to ZONE_NORMAL)
277 After this, memory block XXX's state will be 'online' and the amount of
278 available memory will be increased.
281 This may be changed in future.
292 has to make the whole memory block be unused, memory offline can fail if
293 the memory block includes memory which cannot be freed.
334 If offline succeeds, the state of the memory block is changed to be "offline".
335 If it fails, some error core (like -EBUSY) will be returned by the kernel.
339 A memory block under ZONE_MOVABLE is considered to be able to be offlined
341 block cannot be offlined due to -EBUSY, you can retry offlining it and may be
348 more work. Returning -EBUSY under some situation may be good because the user
367   Generated before new memory becomes available in order to be able to
380   longer possible from the memory but some of the memory to be offlined
381   is still in use. The callback can be used to free memory known to a
391 A callback routine can be registered by calling
419 is (will be) set/clear, if this is -1, then nodemask status is not changed.
421 is (will be) set/clear, if this is -1, then nodemask status is not changed.
422 status_change_nid is set node id when N_MEMORY of nodemask is (will be)