aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Documentation/filesystems/proc.txt33
1 files changed, 33 insertions, 0 deletions
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index 0b3448dba9ec..ff3eb2380831 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -145,6 +145,8 @@ Table 1-1: Process specific entries in /proc
145 stack Report full stack trace, enable via CONFIG_STACKTRACE 145 stack Report full stack trace, enable via CONFIG_STACKTRACE
146 smaps a extension based on maps, showing the memory consumption of 146 smaps a extension based on maps, showing the memory consumption of
147 each mapping and flags associated with it 147 each mapping and flags associated with it
148 numa_maps an extension based on maps, showing the memory locality and
149 binding policy as well as mem usage (in pages) of each mapping.
148.............................................................................. 150..............................................................................
149 151
150For example, to get the status information of a process, all you have to do is 152For example, to get the status information of a process, all you have to do is
@@ -499,6 +501,37 @@ The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
499using /proc/kpageflags and number of times a page is mapped using 501using /proc/kpageflags and number of times a page is mapped using
500/proc/kpagecount. For detailed explanation, see Documentation/vm/pagemap.txt. 502/proc/kpagecount. For detailed explanation, see Documentation/vm/pagemap.txt.
501 503
504The /proc/pid/numa_maps is an extension based on maps, showing the memory
505locality and binding policy, as well as the memory usage (in pages) of
506each mapping. The output follows a general format where mapping details get
507summarized separated by blank spaces, one mapping per each file line:
508
509address policy mapping details
510
51100400000 default file=/usr/local/bin/app kernelpagesize_kB=4 mapped=1 active=0 N3=1
51200600000 default file=/usr/local/bin/app kernelpagesize_kB=4 anon=1 dirty=1 N3=1
5133206000000 default file=/lib64/ld-2.12.so kernelpagesize_kB=4 mapped=26 mapmax=6 N0=24 N3=2
514320621f000 default file=/lib64/ld-2.12.so kernelpagesize_kB=4 anon=1 dirty=1 N3=1
5153206220000 default file=/lib64/ld-2.12.so kernelpagesize_kB=4 anon=1 dirty=1 N3=1
5163206221000 default kernelpagesize_kB=4 anon=1 dirty=1 N3=1
5173206800000 default file=/lib64/libc-2.12.so kernelpagesize_kB=4 mapped=59 mapmax=21 active=55 N0=41 N3=18
518320698b000 default file=/lib64/libc-2.12.so
5193206b8a000 default file=/lib64/libc-2.12.so kernelpagesize_kB=4 anon=2 dirty=2 N3=2
5203206b8e000 default file=/lib64/libc-2.12.so kernelpagesize_kB=4 anon=1 dirty=1 N3=1
5213206b8f000 default kernelpagesize_kB=4 anon=3 dirty=3 active=1 N3=3
5227f4dc10a2000 default kernelpagesize_kB=4 anon=3 dirty=3 N3=3
5237f4dc10b4000 default kernelpagesize_kB=4 anon=2 dirty=2 active=1 N3=2
5247f4dc1200000 default file=/anon_hugepage\040(deleted) huge kernelpagesize_kB=2048 anon=1 dirty=1 N3=1
5257fff335f0000 default stack kernelpagesize_kB=4 anon=3 dirty=3 N3=3
5267fff3369d000 default kernelpagesize_kB=4 mapped=1 mapmax=35 active=0 N3=1
527
528Where:
529"address" is the starting address for the mapping;
530"policy" reports the NUMA memory policy set for the mapping (see vm/numa_memory_policy.txt);
531"mapping details" summarizes mapping data such as mapping type, page usage counters,
532node locality page counters (N0 == node0, N1 == node1, ...) and the kernel page
533size, in KB, that is backing the mapping up.
534
5021.2 Kernel data 5351.2 Kernel data
503--------------- 536---------------
504 537