This is a small cleanup, a breakout from 8185034. See also discussions under that issue.
One thing which makes the code difficult to read is that "Metaspace" means two things: in general, the whole thing. And in particular, one object which holds the memory for a single class loader. So it would make sense to split the Metaspace class:
- a class holding the metaspace memory for a single classloader.
- a class with all the static usability function which do not directly operate on a single metaspace. These functions could be merged with MetaspaceAux, which is already a sink for all kind of static usability functions.
One thing which makes the code difficult to read is that "Metaspace" means two things: in general, the whole thing. And in particular, one object which holds the memory for a single class loader. So it would make sense to split the Metaspace class:
- a class holding the metaspace memory for a single classloader.
- a class with all the static usability function which do not directly operate on a single metaspace. These functions could be merged with MetaspaceAux, which is already a sink for all kind of static usability functions.
- relates to
-
JDK-8185034 Cleanup and consolidate Metaspace coding
-
- Resolved
-