• Home
  • Raw
  • Download

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 * Bits 57-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/vm 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
82 * ``/proc/kpagecgroup``. This file contains a 64-bit inode number of the
83 memory cgroup each page is charged to, indexed by PFN. Only available when
89 0 - LOCKED
91 7 - SLAB
92 page is managed by the SLAB/SLOB/SLUB/SLQB kernel memory allocator
95 10 - BUDDY
96 a free memory block managed by the buddy system allocator
97 The buddy system organizes free memory in blocks of various orders.
100 15 - COMPOUND_HEAD
105 (:ref:`Documentation/admin-guide/mm/hugetlbpage.rst <hugetlbpage>`),
106 the SLUB etc. memory allocators and various device drivers.
109 16 - COMPOUND_TAIL
111 17 - HUGE
113 19 - HWPOISON
114 hardware detected memory corruption on this page: don't touch the data!
115 20 - NOPAGE
117 21 - KSM
118 identical memory pages dynamically shared between one or more processes
119 22 - THP
121 23 - BALLOON
123 24 - ZERO_PAGE
125 25 - IDLE
127 :ref:`Documentation/admin-guide/mm/idle_page_tracking.rst <idle_page_tracking>`).
129 a PTE. To make sure the flag is up-to-date one has to read
133 ---------------------
135 1 - ERROR
137 3 - UPTODATE
138 page has up-to-date data
139 ie. for file backed page: (in-memory data revision >= on-disk one)
140 4 - DIRTY
142 i.e. for file backed page: (in-memory data revision > on-disk one)
143 8 - WRITEBACK
147 ----------------------
149 5 - LRU
151 6 - ACTIVE
153 18 - UNEVICTABLE
154 page is in the unevictable (non-)LRU list It is somehow pinned and
156 shmctl(SHM_LOCK) and mlock() memory segments
157 2 - REFERENCED
159 9 - RECLAIM
161 11 - MMAP
162 a memory mapped page
163 12 - ANON
164 a memory mapped page that is not part of a file
165 13 - SWAPCACHE
166 page is mapped to swap space, i.e. has an associated swap entry
167 14 - SWAPBACKED
170 The page-types tool in the tools/vm directory can be used to query the
176 The general procedure for using pagemap to find out about a process' memory
179 1. Read ``/proc/pid/maps`` to determine which parts of the memory space are
180 mapped to what.
181 2. Select the maps you are interested in -- all of them, or a particular
189 memory that a process is using that is not shared with any other process,
197 Reading from any of the files will return -EINVAL if you are not starting
198 the read on an 8-byte boundary (e.g., if you sought an odd number of bytes
201 Before Linux 3.11 pagemap bits 55-60 were used for "page-shift" (which is
203 after first clear of soft-dirty bits. Since Linux 4.2 they are used for