Lines Matching +full:memory +full:- +full:mapped
12 physical frame each virtual page is mapped to. It contains one 64-bit
16 * Bits 0-54 page frame number (PFN) if present
17 * Bits 0-4 swap type if swapped
18 * Bits 5-54 swap offset if swapped
19 * Bit 55 pte is soft-dirty (see
20 Documentation/admin-guide/mm/soft-dirty.rst)
21 * Bit 56 page exclusively mapped (since 4.2)
22 * Bit 57 pte is uffd-wp write-protected (since 5.13) (see
23 Documentation/admin-guide/mm/userfaultfd.rst)
24 * Bits 58-60 zero
25 * Bit 61 page is file-page or shared-anon (since 3.5)
30 In 4.0 and 4.1 opens by unprivileged fail with -EPERM. Starting from
37 precisely which pages are mapped (or in swap) and comparing mapped
41 determine which areas of memory are actually mapped and llseek to
44 * ``/proc/kpagecount``. This file contains a 64-bit count of the number of
45 times each page is mapped, indexed by PFN.
47 The page-types tool in the tools/mm directory can be used to query the
48 number of times a page is mapped.
50 * ``/proc/kpageflags``. This file contains a 64-bit set of flags for each
83 * ``/proc/kpagecgroup``. This file contains a 64-bit inode number of the
84 memory cgroup each page is charged to, indexed by PFN. Only available when
90 0 - LOCKED
93 7 - SLAB
94 The page is managed by the SLAB/SLUB kernel memory allocator.
97 10 - BUDDY
98 A free memory block managed by the buddy system allocator.
99 The buddy system organizes free memory in blocks of various orders.
102 15 - COMPOUND_HEAD
106 pages are hugeTLB pages (Documentation/admin-guide/mm/hugetlbpage.rst),
107 the SLUB etc. memory allocators and various device drivers.
110 16 - COMPOUND_TAIL
112 17 - HUGE
114 19 - HWPOISON
115 Hardware detected memory corruption on this page: don't touch the data!
116 20 - NOPAGE
118 21 - KSM
119 Identical memory pages dynamically shared between one or more processes.
120 22 - THP
121 Contiguous pages which construct THP of any size and mapped by any granularity.
122 23 - OFFLINE
124 24 - ZERO_PAGE
126 25 - IDLE
128 Documentation/admin-guide/mm/idle_page_tracking.rst).
130 a PTE. To make sure the flag is up-to-date one has to read
132 26 - PGTABLE
136 ---------------------
138 1 - ERROR
140 3 - UPTODATE
141 The page has up-to-date data.
142 ie. for file backed page: (in-memory data revision >= on-disk one)
143 4 - DIRTY
145 i.e. for file backed page: (in-memory data revision > on-disk one)
146 8 - WRITEBACK
150 ----------------------
152 5 - LRU
154 6 - ACTIVE
156 18 - UNEVICTABLE
157 The page is in the unevictable (non-)LRU list It is somehow pinned and
159 shmctl(SHM_LOCK) and mlock() memory segments.
160 2 - REFERENCED
162 9 - RECLAIM
164 11 - MMAP
165 A memory mapped page.
166 12 - ANON
167 A memory mapped page that is not part of a file.
168 13 - SWAPCACHE
169 The page is mapped to swap space, i.e. has an associated swap entry.
170 14 - SWAPBACKED
173 The page-types tool in the tools/mm directory can be used to query the
176 Exceptions for Shared Memory
180 swapped out. This makes swapped out pages indistinguishable from never-allocated
191 holes (none/non-allocated) by specifying the SEEK_DATA flag on the file where
195 mincore() can differentiate between pages in memory (present, including swap
196 cache) and out of memory (swapped out or none/non-allocated).
201 Reading from any of the files will return -EINVAL if you are not starting
202 the read on an 8-byte boundary (e.g., if you sought an odd number of bytes
205 Before Linux 3.11 pagemap bits 55-60 were used for "page-shift" (which is
207 after first clear of soft-dirty bits. Since Linux 4.2 they are used for
217 - Scan the address range and get the memory ranges matching the provided criteria.
219 - Write-protect the pages. The ``PM_SCAN_WP_MATCHING`` is used to write-protect
221 non-Async Write Protected pages are found. The ``PM_SCAN_WP_MATCHING`` can be
223 - Both of those operations can be combined into one atomic operation where we can
228 - ``PAGE_IS_WPALLOWED`` - Page has async-write-protection enabled
229 - ``PAGE_IS_WRITTEN`` - Page has been written to from the time it was write protected
230 - ``PAGE_IS_FILE`` - Page is file backed
231 - ``PAGE_IS_PRESENT`` - Page is present in the memory
232 - ``PAGE_IS_SWAPPED`` - Page is in swapped
233 - ``PAGE_IS_PFNZERO`` - Page has zero PFN
234 - ``PAGE_IS_HUGE`` - Page is PMD-mapped THP or Hugetlb backed
235 - ``PAGE_IS_SOFT_DIRTY`` - Page is soft-dirty
279 The ``PAGE_IS_WRITTEN`` flag can be considered as a better-performing alternative
280 of soft-dirty flag. It doesn't get affected by VMA merging of the kernel and hence
281 the user can find the true soft-dirty pages in case of normal pages. (There may
284 "PAGE_IS_WRITTEN" category is used with uffd write protect-enabled ranges to
285 implement memory dirty tracking in userspace:
290 3. The memory range is registered with ``UFFDIO_REGISTER_MODE_WP`` mode
292 4. Then any part of the registered memory or the whole memory region must