Lines Matching refs:page

1 Split page table lock
4 Originally, mm->page_table_lock spinlock protected all page tables of the
5 mm_struct. But this approach leads to poor page fault scalability of
7 scalability, split page table lock was introduced.
9 With split page table lock we have separate per-table lock to serialize
29 Split page table lock for PTE tables is enabled compile-time if
33 Split page table lock for PMD tables is enabled, if it's enabled for PTE
36 Hugetlb and split page table lock
39 Hugetlb can support several page sizes. We use split lock only for PMD
44 	takes pmd split lock for PMD_SIZE page, mm->page_table_lock
49 Support of split page table lock by an architecture
52 There's no need in special enabling of PTE split page table lock:
56 Make sure the architecture doesn't use slab allocator for page table
57 allocation: slab uses page->slab_cache and page->first_page for its pages.
58 These fields share storage with page->ptl.
60 PMD split lock only makes sense if you have more than two page table
75 page->ptl
78 page->ptl is used to access split page table lock, where 'page' is struct
79 page of page containing the table. It shares storage with page->private
82 To avoid increasing size of struct page and have best performance, we use a
84  - if spinlock_t fits into long, we use page->ptr as spinlock, so we
86  - if size of spinlock_t is bigger then size of long, we use page->ptl as
94 Please, never access page->ptl directly -- use appropriate helper.