-
Enhancement
-
Resolution: Fixed
-
P4
-
17
-
b19
-
linux
- UseHugeTLBFS - explicitly mmap() large pages using MAP_HUGETLB
- UseSHM - create a shared memory segment using shmget() and SHM_HUGETLB
Both these requires that large pages are configured and pre-allocated, the number of currently allocated large pages can be seen with:
> sysctl vm.nr_hugepagessee
See the kernel documentation for more information:
https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt
The share memory approach also requires the process to be privileged (have the capability to lock memory) and that the system is configured to allow large shared memory segments. To get the current max value:
> sysctl kernel.shmmax
There are very few if any pros with the USeSHM approach and we should investigate if we can remove support for it.
If we remove UseSHM, we also can remove UseHugeTLBFS, since it is the negation of the other and now implicitly and unconditionally true if we run with static hugepages.
- csr for
-
JDK-8310841 Obsolete the UseSHM and UseHugeTLBFS flags in JDK 22
-
- Closed
-
- relates to
-
JDK-8318643 +UseTransparentHugePages must enable +UseLargePages
-
- Resolved
-
-
JDK-8319795 Static huge pages are not used for CodeCache
-
- Resolved
-
-
JDK-8261899 Improve warning for UseSHM failures
-
- Open
-
-
JDK-8261896 Add support for multiple large page sizes for UseSHM
-
- Closed
-
-
JDK-8316393 gtest/LargePageGtests.java#use-large-pages-sysV fails os.release_multi_mappings_vm
-
- Closed
-
-
JDK-8261401 Add sanity check for UseSHM large pages similar to the one used with hugetlb large pages
-
- Resolved
-