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 58-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
95 7 - SLAB
96 The page is managed by the SLAB/SLOB/SLUB/SLQB kernel memory allocator.
99 10 - BUDDY
100 A free memory block managed by the buddy system allocator.
101 The buddy system organizes free memory in blocks of various orders.
104 15 - COMPOUND_HEAD
109 (:ref:`Documentation/admin-guide/mm/hugetlbpage.rst <hugetlbpage>`),
110 the SLUB etc. memory allocators and various device drivers.
113 16 - COMPOUND_TAIL
115 17 - HUGE
117 19 - HWPOISON
118 Hardware detected memory corruption on this page: don't touch the data!
119 20 - NOPAGE
121 21 - KSM
122 Identical memory pages dynamically shared between one or more processes.
123 22 - THP
125 23 - OFFLINE
127 24 - ZERO_PAGE
129 25 - IDLE
131 :ref:`Documentation/admin-guide/mm/idle_page_tracking.rst <idle_page_tracking>`).
133 a PTE. To make sure the flag is up-to-date one has to read
135 26 - PGTABLE
139 ---------------------
141 1 - ERROR
143 3 - UPTODATE
144 The page has up-to-date data.
145 ie. for file backed page: (in-memory data revision >= on-disk one)
146 4 - DIRTY
148 i.e. for file backed page: (in-memory data revision > on-disk one)
149 8 - WRITEBACK
153 ----------------------
155 5 - LRU
157 6 - ACTIVE
159 18 - UNEVICTABLE
160 The page is in the unevictable (non-)LRU list It is somehow pinned and
162 shmctl(SHM_LOCK) and mlock() memory segments.
163 2 - REFERENCED
165 9 - RECLAIM
167 11 - MMAP
168 A memory mapped page.
169 12 - ANON
170 A memory mapped page that is not part of a file.
171 13 - SWAPCACHE
172 The page is mapped to swap space, i.e. has an associated swap entry.
173 14 - SWAPBACKED
176 The page-types tool in the tools/vm directory can be used to query the
182 The general procedure for using pagemap to find out about a process' memory
185 1. Read ``/proc/pid/maps`` to determine which parts of the memory space are
186 mapped to what.
187 2. Select the maps you are interested in -- all of them, or a particular
195 memory that a process is using that is not shared with any other process,
200 Exceptions for Shared Memory
204 swapped out. This makes swapped out pages indistinguishable from never-allocated
215 holes (none/non-allocated) by specifying the SEEK_DATA flag on the file where
219 mincore() can differentiate between pages in memory (present, including swap
220 cache) and out of memory (swapped out or none/non-allocated).
225 Reading from any of the files will return -EINVAL if you are not starting
226 the read on an 8-byte boundary (e.g., if you sought an odd number of bytes
229 Before Linux 3.11 pagemap bits 55-60 were used for "page-shift" (which is
231 after first clear of soft-dirty bits. Since Linux 4.2 they are used for