Lines Matching refs:page

5 userspace programs to examine the page tables and related information by
11    physical frame each virtual page is mapped to.  It contains one 64-bit
12    value for each virtual page, containing the following data (from
15     * Bits 0-54  page frame number (PFN) if present
19     * Bit  56    page exclusively mapped (since 4.2)
21     * Bit  61    page is file-page or shared-anon (since 3.5)
22     * Bit  62    page swapped
23     * Bit  63    page present
30    If the page is not present but in swap, then the PFN contains an
31    encoding of the swap file number and the page's offset into the
41    times each page is mapped, indexed by PFN.
44    page, indexed by PFN.
46    The flags are (from fs/proc/page.c, above kpageflags_read):
76    memory cgroup each page is charged to, indexed by PFN. Only available when
79 Short descriptions to the page flags:
82     page is being locked for exclusive access, eg. by undergoing read/write IO
85     page is managed by the SLAB/SLOB/SLUB/SLQB kernel memory allocator
86     When compound page is used, SLUB/SLQB will only set this flag on the head
87     page; SLOB will not flag it at all.
93     set for and _only_ for the first page.
97     A compound page with order N consists of 2^N physically contiguous pages.
98     A compound page with order 2 takes the form of "HTTT", where H donates its
99     head page and T donates its tail page(s).  The major consumers of compound
104     this is an integral part of a HugeTLB page
107     hardware detected memory corruption on this page: don't touch the data!
110     no page frame exists at the requested address
119     balloon compaction page
122     zero page for pfn_zero or huge_zero page
125     page has not been accessed since it was marked idle (see
127     stale in case the page was accessed via a PTE. To make sure the flag
130     [IO related page flags]
132  3. UPTODATE  page has up-to-date data
133               ie. for file backed page: (in-memory data revision >= on-disk one)
134  4. DIRTY     page has been written to, hence contains new data
135               ie. for file backed page: (in-memory data revision >  on-disk one)
136  8. WRITEBACK page is being synced to disk
138     [LRU related page flags]
139  5. LRU         page is in one of the LRU lists
140  6. ACTIVE      page is in the active LRU list
141 18. UNEVICTABLE page is in the unevictable (non-)LRU list
142                 It is somehow pinned and not a candidate for LRU page reclaims,
144  2. REFERENCED  page has been referenced since last LRU list enqueue/requeue
145  9. RECLAIM     page will be reclaimed soon after its pageout IO completed
146 11. MMAP        a memory mapped page
147 12. ANON        a memory mapped page that is not part of a file
148 13. SWAPCACHE   page is mapped to swap space, ie. has an associated swap entry
149 14. SWAPBACKED  page is backed by swap/RAM
151 The page-types tool in the tools/vm directory can be used to query the
164  4. Read a u64 for each page from pagemap.
180 Before Linux 3.11 pagemap bits 55-60 were used for "page-shift" (which is