<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
8008079 G1: Add nextObject routine to CMBitMapRO and replace
nextWord<br>
<a class="moz-txt-link-freetext" href="https://jbs.oracle.com/bugs/browse/JDK-8008079">https://jbs.oracle.com/bugs/browse/JDK-8008079</a><br>
<br>
webrev: <br>
<a class="moz-txt-link-freetext" href="http://cr.openjdk.java.net/~tamao/8008079/webrev.00/">http://cr.openjdk.java.net/~tamao/8008079/webrev.00/</a><br>
<br>
changeset:<br>
<meta charset="utf-8">
When concurrent marking scans an object, the task local finger is
updated to point to the start of the object. If the marking task is
asked to abort, the local finger is updated to the next word where
another could possibly start. When the marking task is restarted, we
restart scanning the marking bitmap from the updated local finger. <br>
<br>
This is a safe implementation but has not been fully exploited for
efficiency because the contents of the marking bitmap should be all
0's until the offset associated with the actual start of the next
object. When the marking task is restarted, we will scan these 0's
looking for the first set bit. <br>
<br>
We can avoid this redundant scanning by updating the finger to and
re-starting the scan at the actual offset where the next object
starts.<br>
<br>
testing:<br>
passed gc-test-suite with stressing marking cycles<br>
script:<br>
./run.sh /home/tamao/jdk1.8.0 --bits 64 --args -tamao -XX:+UseG1GC
-XX:InitiatingHeapOccupancyPercent=10 -XX:+UnlockDiagnosticVMOptions
-XX:+VerifyDuringGC<br>
</body>
</html>