Lines Matching full:table

4 Split page table lock
10 scalability, split page table lock was introduced.
12 With split page table lock we have separate per-table lock to serialize
13 access to the table. At the moment we use split lock for PTE and PMD
16 There are helpers to lock/unlock a table and other accessor functions:
19 	maps pte and takes PTE table lock, returns pointer to the taken
22 	unlocks and unmaps PTE table;
24 	allocates PTE table if needed and take the lock, returns pointer
27 	returns pointer to PTE table lock;
29 	takes PMD table lock, returns pointer to taken lock;
31 	returns pointer to PMD table lock;
33 Split page table lock for PTE tables is enabled compile-time if
37 Split page table lock for PMD tables is enabled, if it's enabled for PTE
40 Hugetlb and split page table lock
52 	returns pointer to table lock;
54 Support of split page table lock by an architecture
57 There's no need in special enabling of PTE split page table lock: everything
59 must be called on PTE table allocation / freeing.
61 Make sure the architecture doesn't use slab allocator for page table
65 PMD split lock only makes sense if you have more than two page table
68 PMD split lock enabling requires pgtable_pmd_page_ctor() call on PMD table
72 pmd_free_tlb(), but make sure you cover all PMD table allocation / freeing
83 page->ptl is used to access split page table lock, where 'page' is struct
84 page of page containing the table. It shares storage with page->private
97 The spinlock_t allocated in pgtable_pte_page_ctor() for PTE table and in
98 pgtable_pmd_page_ctor() for PMD table.