ie.
-// The default length of mutex name was originally chosen to be 64 to avoid
-// false sharing. Now, PaddedMutex and PaddedMonitor are available for this purpose.
-// TODO: Check if _name[MUTEX_NAME_LEN] should better get replaced by const char*.
-static const int MUTEX_NAME_LEN = 64;
-
Since HandshakeState embeds Mutex, it adds 512 extra bits to JavaThread.
I ran performance tests on this and there was no change in performance.
-// The default length of mutex name was originally chosen to be 64 to avoid
-// false sharing. Now, PaddedMutex and PaddedMonitor are available for this purpose.
-// TODO: Check if _name[MUTEX_NAME_LEN] should better get replaced by const char*.
-static const int MUTEX_NAME_LEN = 64;
-
Since HandshakeState embeds Mutex, it adds 512 extra bits to JavaThread.
I ran performance tests on this and there was no change in performance.
- relates to
-
JDK-8265682 G1: Mutex::_name dangling in HeapRegionRemSet references after JDK-8264146
-
- Resolved
-
-
JDK-8265921 Mutex name may point to garbage after JDK-8264146
-
- Closed
-
-
JDK-6610420 Debug VM crashes during monitor lock rank checking
-
- Closed
-
-
JDK-8166970 Adapt mutex padding according to DEFAULT_CACHE_LINE_SIZE
-
- Resolved
-
(1 links to)