JDK-8257757 : Never use multiple page sizes for a memory reservation for a ReservedSpace
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 16
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2020-12-04
  • Updated: 2021-01-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8259496 - Parallel GC insists on using large pages although it failed to use them
Description
A ReservedSpace can sometimes have an underlying mapping on Linux that uses more than one page sizes. This happens when a mapping is requested to use large pages but the size of the reservation is not aligned to the large page size. This is handled by:
os::Linux::reserve_memory_special_huge_tlbfs_mixed(...)

We should investigate if this functionality is needed or if we could simplify this to guarantee that a ReservedSpace will consist of a mapping with only one page size. If we have that the ReservedSpace could keep the page size it was mapped with and we would not need helpers trying to estimate the page size like:
ReservedSpace::actual_reserved_page_size(...)

There has been a side discussion about this in a recent PR that added the above mentioned helper, for some more background please see:
https://github.com/openjdk/jdk/pull/1161