Lines Matching refs:memory
45 3.9 /proc/<pid>/map_files - Information about memory mapped files
141 statm Process memory status information
147 smaps a extension based on maps, showing the memory consumption of
149 numa_maps an extension based on maps, showing the memory locality and
200 memory usage. Its seven fields are explained in Table 1-3. The stat file
230 VmPeak peak virtual memory size
232 VmLck locked memory size
234 VmRSS size of memory portions
242 HugetlbPages size of hugetlb memory portions
257 Mems_allowed mask of memory nodes allowed to this process
267 resident size of memory portions (pages) (same as VmRSS in status)
304 vsize virtual memory size
305 rss resident set memory size
336 The /proc/PID/maps file containing the currently mapped memory regions and
375 with the memory region, as the case would be with BSS (uninitialized data).
387 The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint
415 The /proc/PID/smaps is an extension based on maps, showing the memory
446 in memory, where each page is divided by the number of processes sharing it.
452 "Referenced" indicates the amount of memory currently marked as referenced or
454 "Anonymous" shows the amount of memory that does not belong to any file. Even
457 "AnonHugePages" shows the ammount of memory backed by transparent hugepage.
458 "Shared_Hugetlb" and "Private_Hugetlb" show the ammounts of memory backed by
461 "Swap" shows how much would-be-anonymous memory is also used, but out on swap.
463 "Locked" indicates whether the mapping is locked in memory or not.
466 flags associated with the particular virtual memory area in two letter encoded
479 lo - pages are locked in memory
480 io - memory mapped I/O area
528 The /proc/pid/numa_maps is an extension based on maps, showing the memory
529 locality and binding policy, as well as the memory usage (in pages) of
554 "policy" reports the NUMA memory policy set for the mapping (see vm/numa_memory_policy.txt);
572 buddyinfo Kernel memory allocator information (see text) (2.5)
674 (typically counting ECC corrected errors of memory or cache) exceeds
752 The slabinfo file gives information about memory usage at the slab level.
753 Linux uses slab pools for memory management above page level in version 2.2.
799 migrate types into the same contiguous regions of memory called page blocks.
813 unless memory has been mlock()'d. Some of the Reclaimable blocks should
821 Provides information about distribution and utilization of memory. This
862 MemAvailable: An estimate of how much memory is available for starting new
872 Cached: in-memory cache for files read from the disk (the
875 still also is in the swapfile (if memory is needed it
883 HighFree: Highmem is all memory above ~860MB of physical memory
886 this memory, making it slower to access than lowmem.
888 LowFree: Lowmem is memory which can be used for everything that
903 SUnreclaim: Part of Slab, that cannot be reclaimed on memory pressure
904 PageTables: amount of memory dedicated to the lowest level of page
911 this is the total amount of memory currently available to
921 For more details, see the memory overcommit documentation
923 Committed_AS: The amount of memory presently allocated on the system.
924 The committed memory is a sum of all of the memory which
927 of memory, but only touches 300M of it will show up as
928 using 1G. This 1G is memory which has been "committed" to
934 not fail due to lack of memory once that memory has been
936 VmallocTotal: total size of vmalloc memory area
957 Number of pages allocated on memory node <node>
1441 process gets killed in out of memory conditions.
1445 units are roughly a proportion along that range of allowed memory the process
1446 may allocate from based on an estimation of its current memory and swap use.
1447 For example, if a task is using all allowed memory, its badness score will be
1448 1000. If it is using half of its allowed memory, its score will be 500.
1450 There is an additional factor included in the badness score: the current memory
1453 The amount of "allowed" memory depends on the context in which the oom killer
1454 was called. If it is due to the memory assigned to the allocating task's cpuset
1455 being exhausted, the allowed memory represents the set of mems assigned to that
1457 memory represents the set of mempolicy nodes. If it is due to a memory
1458 limit (or swap limit) being reached, the allowed memory is that configured
1459 limit. Finally, if it is due to the entire system being out of memory, the
1460 allowed memory represents all allocatable resources.
1470 Consequently, it is very simple for userspace to define the amount of memory to
1473 same system, cpuset, mempolicy, or memory controller resources to use at least
1474 50% more memory. A value of -500, on the other hand, would be roughly
1475 equivalent to discounting 50% of the task's allowed memory from being considered
1499 process should be killed in an out-of-memory situation.
1606 When a process is dumped, all anonymous memory is written to a core file as
1608 to dump some memory segments, for example, huge shared memory or DAX.
1609 Conversely, sometimes we want to save file-backed memory segments into a core
1612 /proc/<pid>/coredump_filter allows you to customize which memory segments
1614 of memory types. If a bit of the bitmask is set, memory segments of the
1615 corresponding memory type are dumped, otherwise they are not dumped.
1617 The following 9 memory types are supported:
1618 - (bit 0) anonymous private memory
1619 - (bit 1) anonymous shared memory
1620 - (bit 2) file-backed private memory
1621 - (bit 3) file-backed shared memory
1622 - (bit 4) ELF header pages in file-backed private memory areas (it is
1624 - (bit 5) hugetlb private memory
1625 - (bit 6) hugetlb shared memory
1626 - (bit 7) DAX private memory
1627 - (bit 8) DAX shared memory
1632 Note that bits 0-4 don't affect hugetlb or DAX memory. hugetlb memory is
1635 The default value of coredump_filter is 0x33; this means all anonymous memory
1636 segments, ELF header pages and hugetlb private memory are dumped.
1638 If you don't want to dump all shared memory segments attached to pid 1234,
1831 3.9 /proc/<pid>/map_files - Information about memory mapped files
1833 This directory contains symbolic links which represent memory mapped files
1843 The name of a link represents the virtual memory bounds of a mapping, i.e.
1846 The main purpose of the map_files is to retrieve a set of memory mapped
1850 comparing their inode numbers to figure out which anonymous memory areas