Searched refs:smaps (Results 1 – 6 of 6) sorted by relevance
| /Linux-v5.4/tools/testing/selftests/vm/ |
| D | mlock-random-test.c | 87 FILE *smaps; in get_proc_page_size() local 92 smaps = seek_to_smaps_entry(addr); in get_proc_page_size() 93 if (!smaps) { in get_proc_page_size() 98 while (getline(&line, &size, smaps) > 0) { in get_proc_page_size() 116 if (smaps) in get_proc_page_size() 117 fclose(smaps); in get_proc_page_size()
|
| D | mlock2-tests.c | 131 FILE *smaps; in is_vmflag_set() local 133 smaps = seek_to_smaps_entry(addr); in is_vmflag_set() 134 if (!smaps) { in is_vmflag_set() 139 while (getline(&line, &size, smaps) > 0) { in is_vmflag_set() 154 fclose(smaps); in is_vmflag_set() 166 FILE *smaps = NULL; in is_vma_lock_on_fault() local 176 smaps = seek_to_smaps_entry(addr); in is_vma_lock_on_fault() 177 if (!smaps) { in is_vma_lock_on_fault() 182 while (getline(&line, &size, smaps) > 0) { in is_vma_lock_on_fault() 198 while (getline(&line, &size, smaps) > 0) { in is_vma_lock_on_fault() [all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | procfs-smaps_rollup | 6 process. The format is almost identical to /proc/pid/smaps, 10 fields from all the maps in /proc/pid/smaps. 12 are not present in /proc/pid/smaps. These fields represent
|
| /Linux-v5.4/fs/proc/ |
| D | Kconfig | 89 /proc/pid/smaps, /proc/pid/clear_refs, /proc/pid/pagemap,
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 284 it is necessary to read ``/proc/PID/smaps`` and count the AnonHugePages fields 290 is necessary to read ``/proc/PID/smaps`` and count the FileHugeMapped fields 293 Note that reading the smaps file is expensive and reading it
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | proc.txt | 140 clear_refs Clears page referenced bits shown in smaps output 157 smaps An extension based on maps, showing the memory consumption of 159 smaps_rollup Accumulated smaps stats for all mappings of the process. This 160 can be derived from smaps, but is faster and more convenient 227 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table. 421 The /proc/PID/smaps is an extension based on maps, showing the memory 532 Note: reading /proc/PID/maps or /proc/PID/smaps is inherently racy (consistent 541 life of the smaps/maps walk, there will be some output for it. 543 The /proc/PID/smaps_rollup file includes the same fields as /proc/PID/smaps, 552 described for smaps above. These fields are omitted in smaps since each [all …]
|