Lines Matching +full:memory +full:- +full:mapped
14 physical frame each virtual page is mapped to. It contains one 64-bit
18 * Bits 0-54 page frame number (PFN) if present
19 * Bits 0-4 swap type if swapped
20 * Bits 5-54 swap offset if swapped
21 * Bit 55 pte is soft-dirty (see
22 :ref:`Documentation/admin-guide/mm/soft-dirty.rst <soft_dirty>`)
23 * Bit 56 page exclusively mapped (since 4.2)
24 * Bit 57 pte is uffd-wp write-protected (since 5.13) (see
25 :ref:`Documentation/admin-guide/mm/userfaultfd.rst <userfaultfd>`)
26 * Bits 57-60 zero
27 * Bit 61 page is file-page or shared-anon (since 3.5)
32 In 4.0 and 4.1 opens by unprivileged fail with -EPERM. Starting from
39 precisely which pages are mapped (or in swap) and comparing mapped
43 determine which areas of memory are actually mapped and llseek to
46 * ``/proc/kpagecount``. This file contains a 64-bit count of the number of
47 times each page is mapped, indexed by PFN.
49 The page-types tool in the tools/vm directory can be used to query the
50 number of times a page is mapped.
52 * ``/proc/kpageflags``. This file contains a 64-bit set of flags for each
85 * ``/proc/kpagecgroup``. This file contains a 64-bit inode number of the
86 memory cgroup each page is charged to, indexed by PFN. Only available when
92 0 - LOCKED
94 7 - SLAB
95 page is managed by the SLAB/SLOB/SLUB/SLQB kernel memory allocator
98 10 - BUDDY
99 a free memory block managed by the buddy system allocator
100 The buddy system organizes free memory in blocks of various orders.
103 15 - COMPOUND_HEAD
108 (:ref:`Documentation/admin-guide/mm/hugetlbpage.rst <hugetlbpage>`),
109 the SLUB etc. memory allocators and various device drivers.
112 16 - COMPOUND_TAIL
114 17 - HUGE
116 19 - HWPOISON
117 hardware detected memory corruption on this page: don't touch the data!
118 20 - NOPAGE
120 21 - KSM
121 identical memory pages dynamically shared between one or more processes
122 22 - THP
124 23 - OFFLINE
126 24 - ZERO_PAGE
128 25 - IDLE
130 :ref:`Documentation/admin-guide/mm/idle_page_tracking.rst <idle_page_tracking>`).
132 a PTE. To make sure the flag is up-to-date one has to read
134 26 - PGTABLE
138 ---------------------
140 1 - ERROR
142 3 - UPTODATE
143 page has up-to-date data
144 ie. for file backed page: (in-memory data revision >= on-disk one)
145 4 - DIRTY
147 i.e. for file backed page: (in-memory data revision > on-disk one)
148 8 - WRITEBACK
152 ----------------------
154 5 - LRU
156 6 - ACTIVE
158 18 - UNEVICTABLE
159 page is in the unevictable (non-)LRU list It is somehow pinned and
161 shmctl(SHM_LOCK) and mlock() memory segments
162 2 - REFERENCED
164 9 - RECLAIM
166 11 - MMAP
167 a memory mapped page
168 12 - ANON
169 a memory mapped page that is not part of a file
170 13 - SWAPCACHE
171 page is mapped to swap space, i.e. has an associated swap entry
172 14 - SWAPBACKED
175 The page-types tool in the tools/vm directory can be used to query the
181 The general procedure for using pagemap to find out about a process' memory
184 1. Read ``/proc/pid/maps`` to determine which parts of the memory space are
185 mapped to what.
186 2. Select the maps you are interested in -- all of them, or a particular
194 memory that a process is using that is not shared with any other process,
202 Reading from any of the files will return -EINVAL if you are not starting
203 the read on an 8-byte boundary (e.g., if you sought an odd number of bytes
206 Before Linux 3.11 pagemap bits 55-60 were used for "page-shift" (which is
208 after first clear of soft-dirty bits. Since Linux 4.2 they are used for