RFR: 8296231: Fix MEMFLAGS for CHeapBitMaps
Thomas Stuefe
stuefe at openjdk.org
Wed Nov 2 14:59:13 UTC 2022
On Wed, 2 Nov 2022 14:24:07 GMT, Stefan Karlsson <stefank at openjdk.org> wrote:
> I'd prefer to remove the default value, but there is currently a PR touching the BitMap classes, so I'd like to limit this Bug to only fixing the incorrect usage of mtInternal.
I always wanted something like a thread-bound default Memflags, that could be set with something like MemFlagsMark. It would define the Memflags to be used for the extent if no explicit Memflags are given. This would make sense, especially for utility classes that are used on behalf of other code. For example, wherever we dive into Metaspace allocation, we set the default flag to mtMetaspace, which is probably a good default for all subsequent mallocs in this extent.
What do you think?
-------------
PR: https://git.openjdk.org/jdk/pull/10948
More information about the hotspot-dev
mailing list