Lines Matching full:block

85 size of a memory block is architecture dependent and represents the logical
87 default size of a memory block is the same as memory section size unless an
90 To determine the size (in bytes) of a memory block please read this file::
126 All memory blocks have their device information in sysfs.  Each memory block
131 where XXX is the memory block id.
133 For the memory block covered by the sysfs directory.  It is expected that all
137 block.
139 For example, assume 1GiB memory block size. A device for a memory starting at
146 Under each memory block, you can see 5 files:
155 ``phys_index``      read-only and contains memory block id, same as XXX.
162                     which will be performed on all sections in the block.
166                     whether the memory block is removable or not
168                     block is removable and a value of 0 indicates that
169                     it is not removable. A memory block is removable only if
170                     every section in the block is removable.
171 ``valid_zones``     read-only: designed to show which zones this memory block
254 To see (online/offline) state of a memory block, read 'state' file::
259 - If the memory block is online, you'll read "online".
260 - If the memory block is offline, you'll read "offline".
287 If the automatic onlining wasn't requested, failed, or some memory block was
288 offlined it is possible to change the individual block's state by writing to the
293 This onlining will not change the ZONE type of the target memory block,
294 If the memory block doesn't belong to any zone an appropriate kernel zone
302 .. note:: current limit: this memory block must be adjacent to ZONE_MOVABLE
308 .. note:: current limit: this memory block must be adjacent to ZONE_NORMAL
313 After this, memory block XXX's state will be 'online' and the amount of
325 has to make the whole memory block be unused, memory offline can fail if
326 the memory block includes memory which cannot be freed.
330 (1) reclaim and free all memory in the memory block.
331 (2) migrate all pages in the memory block.
334 all  pages in the memory block by page migration. But not all pages are
336 page caches. For offlining a memory block by migration, the kernel has to
337 guarantee that the memory block contains only migratable pages.
339 Now, a boot option for making a memory block which consists of migratable pages
357    Unfortunately, there is no information to show which memory block belongs
365 You can offline a memory block by using the same sysfs interface that was used
370 If offline succeeds, the state of the memory block is changed to be "offline".
372 Even if a memory block does not belong to ZONE_MOVABLE, you can try to offline
375 A memory block under ZONE_MOVABLE is considered to be able to be offlined
377 block cannot be offlined due to -EBUSY, you can retry offlining it and may be
399 When adding/removing memory that uses memory block devices (i.e. ordinary RAM),
403   block devices can only be accessed (.online/.state attributes) by user
440   - showing memory block and physical device relationship.