Knowing what page size was used for a mapping can sometimes be needed. Either for logging or to figure out a suitable chunk-size when pretouching memory. Currently we have a helper function `ReservedSpace::actual_reserved_page_size()` that looks at the `ReservedSpace` and tries to figure out what page size was used.
As long as only large page size can be used in the VM this works well. But if we enable the JVM to use more than one large page size, (seeJDK-8256155) this helper will not be enough.
A better solution would be to extend the reservation APIs to pass back the page size used for a mapping and then record this in the ReservedSpace.
As long as only large page size can be used in the VM this works well. But if we enable the JVM to use more than one large page size, (see
A better solution would be to extend the reservation APIs to pass back the page size used for a mapping and then record this in the ReservedSpace.
- relates to
-
JDK-8266349 Pass down requested page size to reserve_memory_special
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
JDK-8261029 Code heap page sizes not traced correctly using os::trace_page_sizes
-
- Resolved
-
-
-
- Resolved
-
(1 relates to, 2 links to)