Lines Matching refs:block

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:
135 All memory blocks have their device information in sysfs.  Each memory block
139 (XXX is the memory block id.)
141 For the memory block covered by the sysfs directory.  It is expected that all
145 block.
147 For example, assume 1GiB memory block size. A device for a memory starting at
152 Under each memory block, you can see 5 files:
160 'phys_index'      : read-only and contains memory block id, same as XXX.
165                     which will be performed on all sections in the block.
169                     whether the memory block is removable or not
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.
174 'valid_zones'     : read-only: designed to show which zones this memory block
248 To see (online/offline) state of a memory block, read 'state' file.
253 If the memory block is online, you'll read "online".
254 If the memory block is offline, you'll read "offline".
260 For using newly added memory, you have to "online" the memory block.
262 For onlining, you have to write "online" to the memory block's state file as:
266 This onlining will not change the ZONE type of the target memory block,
267 If the memory block is in ZONE_NORMAL, you can change it to ZONE_MOVABLE:
270 (NOTE: current limit: this memory block must be adjacent to ZONE_MOVABLE)
272 And if the memory block is in ZONE_MOVABLE, you can change it to ZONE_NORMAL:
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
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.
297 (1) reclaim and free all memory in the memory block.
298 (2) migrate all pages in the memory block.
301 all  pages in the memory block by page migration. But not all pages are
303 page caches. For offlining a memory block by migration, the kernel has to
304 guarantee that the memory block contains only migratable pages.
306 Now, a boot option for making a memory block which consists of migratable pages
323 Note: Unfortunately, there is no information to show which memory block belongs
329 You can offline a memory block by using the same sysfs interface that was used
334 If offline succeeds, the state of the memory block is changed to be "offline".
336 Even if a memory block does not belong to ZONE_MOVABLE, you can try to offline
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
382   subsystem from the indicated memory block.
386   the memory block that we attempted to offline.
403 The first argument of the callback function (self) is a pointer to the block
445   - showing memory block and physical device relationship.