- 1.9.0 (latest)
- 1.8.0
- 1.7.0
- 1.6.1
- 1.5.0
- 1.4.0
- 1.3.0
- 1.2.0
- 1.1.1
- 1.0.0
- 0.42.0
- 0.41.0
- 0.40.0
- 0.39.0
- 0.38.0
- 0.37.0
- 0.36.0
- 0.35.0
- 0.34.1
- 0.33.1
- 0.32.0
- 0.31.0
- 0.30.0
- 0.29.0
- 0.28.0
- 0.27.0
- 0.26.0
- 0.25.0
- 0.24.0
- 0.23.0
- 0.22.0
- 0.21.1
- 0.20.0
- 0.19.0
- 0.18.0
- 0.17.0
- 0.16.3
- 0.15.0
- 0.14.0
- 0.13.0
- 0.12.0
- 0.11.0
- 0.10.0
- 0.9.1
- 0.8.0
- 0.7.3
Reference documentation and code samples for the Kubernetes Engine V1 API module Google::Cloud::Container::V1::LinuxNodeConfig::TransparentHugepageDefrag.
Possible values for transparent hugepage defrag support.
Constants
TRANSPARENT_HUGEPAGE_DEFRAG_UNSPECIFIED
value: 0
Default value. GKE will not modify the kernel configuration.
TRANSPARENT_HUGEPAGE_DEFRAG_ALWAYS
value: 1
It means that an application requesting THP will stall on allocation
failure and directly reclaim pages and compact memory in an effort to
allocate a THP immediately.
TRANSPARENT_HUGEPAGE_DEFRAG_DEFER
value: 2
It means that an application will wake kswapd in the background to
reclaim pages and wake kcompactd to compact memory so that THP is
available in the near future. It’s the responsibility of khugepaged to
then install the THP pages later.
TRANSPARENT_HUGEPAGE_DEFRAG_DEFER_WITH_MADVISE
value: 3
It means that an application will enter direct reclaim and compaction
like always, but only for regions that have used madvise(MADV_HUGEPAGE);
all other regions will wake kswapd in the background to reclaim pages and
wake kcompactd to compact memory so that THP is available in the near
future.
TRANSPARENT_HUGEPAGE_DEFRAG_MADVISE
value: 4
It means that an application will enter direct reclaim like always but
only for regions that are have used madvise(MADV_HUGEPAGE). This is the
default kernel configuration.
TRANSPARENT_HUGEPAGE_DEFRAG_NEVER
value: 5
It means that an application will never enter direct reclaim or
compaction.