admin-guide/mm/transhuge.rst

52 disabled, there is ``khugepaged`` daemon that scans memory and
70 is by far not mandatory and khugepaged already can take care of long
134 	of khugepaged to then install the THP pages later.
163 khugepaged will be automatically started when
170 khugepaged runs usually at low frequency so while one may not want to
172 should be worth invoking defrag at least in khugepaged. However it's
173 also possible to disable defrag in khugepaged by writing 0 or enable
174 defrag in khugepaged by writing 1::
176 	echo 0 >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
177 	echo 1 >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
179 You can also control how many pages khugepaged should scan at each
182 	/sys/kernel/mm/transparent_hugepage/khugepaged/pages_to_scan
184 and how many milliseconds to wait in khugepaged between each pass (you
185 can set this to 0 to run khugepaged at 100% utilization of one core)::
187 	/sys/kernel/mm/transparent_hugepage/khugepaged/scan_sleep_millisecs
189 and how many milliseconds to wait in khugepaged if there's an hugepage
192 	/sys/kernel/mm/transparent_hugepage/khugepaged/alloc_sleep_millisecs
194 The khugepaged progress can be seen in the number of pages collapsed::
196 	/sys/kernel/mm/transparent_hugepage/khugepaged/pages_collapsed
200 	/sys/kernel/mm/transparent_hugepage/khugepaged/full_scans
206 	/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_none
216 	/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_swap
226 	/sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_shared
283 regions registered in khugepaged.
311 	is incremented by khugepaged when it has found
325 	is incremented if khugepaged found a range