Lines Matching full:enabled

63 THP can be enabled system wide or restricted to certain tasks or even
87 In certain cases when hugepages are enabled system wide, application
111 (mostly for debugging purposes) or only enabled inside MADV_HUGEPAGE
112 regions (to avoid the risk of consuming more memory resources) or enabled
115 	echo always >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
116 	echo madvise >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
117 	echo never >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
124 	echo always >/sys/kernel/mm/transparent_hugepage/hugepages-2048kB/enabled
127 will inherit the top-level "enabled" value::
129 	echo inherit >/sys/kernel/mm/transparent_hugepage/hugepages-<size>kB/enabled
133 	echo inherit >/sys/kernel/mm/transparent_hugepage/hugepages-2048kB/enabled
138 	echo always >/sys/kernel/mm/transparent_hugepage/enabled
139 	echo madvise >/sys/kernel/mm/transparent_hugepage/enabled
140 	echo never >/sys/kernel/mm/transparent_hugepage/enabled
142 By default, PMD-sized hugepages have enabled="inherit" and all other
143 hugepage sizes have enabled="never". If enabling multiple hugepage
144 sizes, the kernel will select the most appropriate enabled size for a
206 sizes are enabled (either by directly setting "always" or "madvise",
207 or by setting "inherit" while the top-level enabled is set to "always"
210 setting "inherit" while the top-level enabled is set to "never").
337 The transparent_hugepage/enabled and
338 transparent_hugepage/hugepages-<size>kB/enabled values and tmpfs mount
483 support enabled just fine as always. No difference can be noted in