Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2201448 | 7 | John Cuthbertson | P4 | Closed | Fixed | b115 |
JDK-2205796 | 6u25 | John Cuthbertson | P4 | Resolved | Fixed | b01 |
In 6940310 we introduced versions of the push() and pop() methods on the CMRegionStack class that use locks to deal with failures that were caused by the MT-unsafe use of the lock-free push() and pop() versions (push() can be called concurrently, pop() can be called concurrently, but push() cannot be called concurrently with pop()). However, for performance and scalability reasons, it'd be good to go back to use the lock-free versions.
- backported by
-
JDK-2205796 G1: use only lock-free versions of region stack push() and pop()
- Resolved
-
JDK-2201448 G1: use only lock-free versions of region stack push() and pop()
- Closed
- relates to
-
JDK-6940310 G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop()
- Resolved
-
JDK-6988458 G1: assert(mr.end() <= _cm->finger()) failed: otherwise the region shouldn't be on the stack
- Resolved