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
199 memory usage. Its seven fields are explained in Table 1-3. The stat file
229 VmPeak peak virtual memory size
231 VmLck locked memory size
233 VmRSS size of memory portions
254 Mems_allowed mask of memory nodes allowed to this process
264 resident size of memory portions (pages) (same as VmRSS in status)
301 vsize virtual memory size
302 rss resident set memory size
333 The /proc/PID/maps file containing the currently mapped memory regions and
372 with the memory region, as the case would be with BSS (uninitialized data).
384 The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint
412 The /proc/PID/smaps is an extension based on maps, showing the memory
439 indicates the amount of memory currently marked as referenced or accessed.
440 "Anonymous" shows the amount of memory that does not belong to any file. Even
443 "Swap" shows how much would-be-anonymous memory is also used, but out on
447 flags associated with the particular virtual memory area in two letter encoded
460 lo - pages are locked in memory
461 io - memory mapped I/O area
510 The /proc/pid/numa_maps is an extension based on maps, showing the memory
511 locality and binding policy, as well as the memory usage (in pages) of
536 "policy" reports the NUMA memory policy set for the mapping (see vm/numa_memory_policy.txt);
554 buddyinfo Kernel memory allocator information (see text) (2.5)
656 (typically counting ECC corrected errors of memory or cache) exceeds
734 The slabinfo file gives information about memory usage at the slab level.
735 Linux uses slab pools for memory management above page level in version 2.2.
781 migrate types into the same contiguous regions of memory called page blocks.
795 unless memory has been mlock()'d. Some of the Reclaimable blocks should
803 Provides information about distribution and utilization of memory. This
809 The "Locked" indicates whether the mapping is locked in memory or not.
847 MemAvailable: An estimate of how much memory is available for starting new
857 Cached: in-memory cache for files read from the disk (the
860 still also is in the swapfile (if memory is needed it
868 HighFree: Highmem is all memory above ~860MB of physical memory
871 this memory, making it slower to access than lowmem.
873 LowFree: Lowmem is memory which can be used for everything that
888 SUnreclaim: Part of Slab, that cannot be reclaimed on memory pressure
889 PageTables: amount of memory dedicated to the lowest level of page
896 this is the total amount of memory currently available to
906 For more details, see the memory overcommit documentation
908 Committed_AS: The amount of memory presently allocated on the system.
909 The committed memory is a sum of all of the memory which
912 of memory, but only touches 300M of it will show up as
913 using 1G. This 1G is memory which has been "committed" to
919 not fail due to lack of memory once that memory has been
921 VmallocTotal: total size of vmalloc memory area
942 Number of pages allocated on memory node <node>
1426 process gets killed in out of memory conditions.
1430 units are roughly a proportion along that range of allowed memory the process
1431 may allocate from based on an estimation of its current memory and swap use.
1432 For example, if a task is using all allowed memory, its badness score will be
1433 1000. If it is using half of its allowed memory, its score will be 500.
1435 There is an additional factor included in the badness score: the current memory
1438 The amount of "allowed" memory depends on the context in which the oom killer
1439 was called. If it is due to the memory assigned to the allocating task's cpuset
1440 being exhausted, the allowed memory represents the set of mems assigned to that
1442 memory represents the set of mempolicy nodes. If it is due to a memory
1443 limit (or swap limit) being reached, the allowed memory is that configured
1444 limit. Finally, if it is due to the entire system being out of memory, the
1445 allowed memory represents all allocatable resources.
1455 Consequently, it is very simple for userspace to define the amount of memory to
1458 same system, cpuset, mempolicy, or memory controller resources to use at least
1459 50% more memory. A value of -500, on the other hand, would be roughly
1460 equivalent to discounting 50% of the task's allowed memory from being considered
1484 process should be killed in an out-of-memory situation.
1591 When a process is dumped, all anonymous memory is written to a core file as
1593 to dump some memory segments, for example, huge shared memory. Conversely,
1594 sometimes we want to save file-backed memory segments into a core file, not
1597 /proc/<pid>/coredump_filter allows you to customize which memory segments
1599 of memory types. If a bit of the bitmask is set, memory segments of the
1600 corresponding memory type are dumped, otherwise they are not dumped.
1602 The following 7 memory types are supported:
1603 - (bit 0) anonymous private memory
1604 - (bit 1) anonymous shared memory
1605 - (bit 2) file-backed private memory
1606 - (bit 3) file-backed shared memory
1607 - (bit 4) ELF header pages in file-backed private memory areas (it is
1609 - (bit 5) hugetlb private memory
1610 - (bit 6) hugetlb shared memory
1615 Note bit 0-4 doesn't effect any hugetlb memory. hugetlb memory are only
1618 Default value of coredump_filter is 0x23; this means all anonymous memory
1619 segments and hugetlb private memory are dumped.
1621 If you don't want to dump all shared memory segments attached to pid 1234,
1814 3.9 /proc/<pid>/map_files - Information about memory mapped files
1816 This directory contains symbolic links which represent memory mapped files
1826 The name of a link represents the virtual memory bounds of a mapping, i.e.
1829 The main purpose of the map_files is to retrieve a set of memory mapped
1833 comparing their inode numbers to figure out which anonymous memory areas