See discussion under [1].
Since the libc malloc allocator may place ObjectMonitor instances adjacent to each other, we should pad the size of ObjectMonitor to fill a whole cache line to prevent false sharing between adjacent OMs.
[1] https://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2022-March/054187.html
Since the libc malloc allocator may place ObjectMonitor instances adjacent to each other, we should pad the size of ObjectMonitor to fill a whole cache line to prevent false sharing between adjacent OMs.
[1] https://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2022-March/054187.html
- relates to
-
JDK-8049737 Contended Locking reorder and cache line bucket
-
- Closed
-
-
JDK-8253064 monitor list simplifications and getting rid of TSM
-
- Resolved
-
- links to
-
Review
openjdk/jdk/7955