Lines Matching refs:khugepaged

51   automatically (with khugepaged)
76 is by far not mandatory and khugepaged already can take care of long
126 khugepaged will be automatically started when
130 khugepaged runs usually at low frequency so while one may not want to
132 should be worth invoking defrag at least in khugepaged. However it's
133 also possible to disable defrag in khugepaged by writing 0 or enable
134 defrag in khugepaged by writing 1:
136 echo 0 >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
137 echo 1 >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
139 You can also control how many pages khugepaged should scan at each
142 /sys/kernel/mm/transparent_hugepage/khugepaged/pages_to_scan
144 and how many milliseconds to wait in khugepaged between each pass (you
145 can set this to 0 to run khugepaged at 100% utilization of one core):
147 /sys/kernel/mm/transparent_hugepage/khugepaged/scan_sleep_millisecs
149 and how many milliseconds to wait in khugepaged if there's an hugepage
152 /sys/kernel/mm/transparent_hugepage/khugepaged/alloc_sleep_millisecs
154 The khugepaged progress can be seen in the number of pages collapsed:
156 /sys/kernel/mm/transparent_hugepage/khugepaged/pages_collapsed
160 /sys/kernel/mm/transparent_hugepage/khugepaged/full_scans
166 /sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_none
185 the regions registered in khugepaged.
203 thp_collapse_alloc is incremented by khugepaged when it has found
210 thp_collapse_alloc_failed is incremented if khugepaged found a range
340 created from under you by khugepaged (khugepaged collapse_huge_page