RFR: 8272083: G1: Record iterated range for BOT performance during card scan [v5]

[Yude Lin]

> A fix to the problem in 8272083 is to use a per-worker pointer to indicate where the worker has scanned up to, similar to the _scanned_to variable. The difference is this pointer (I call it _iterated_to) records the end of the object and _scanned_to records the end of the scan. Since we always scan with increasing addresses, the end of the latest object scanned is also the address where BOT has fixed up to. So we avoid having to fix below this address when calling block_start(). This implementation approximately reduce the number of calls to set_offset_array() during scan_heap_roots() 2-10 times (in my casual test with -XX:G1ConcRefinementGreenZone=1000000).
> 
> What this approach not solving is random access to BOT. So far I haven't found anything having this pattern.

Yude Lin has updated the pull request incrementally with three additional commits since the last revision:

 - Removed additional thread and card set code
 - Switch to dcq and refinement threads to manage the plab cards
 - Trivial

-------------

Changes:
  - all: https://git.openjdk.java.net/jdk/pull/5039/files
  - new: https://git.openjdk.java.net/jdk/pull/5039/files/1fc721f1..c4331668

Webrevs:
 - full: https://webrevs.openjdk.java.net/?repo=jdk&pr=5039&range=04
 - incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=5039&range=03-04

  Stats: 1235 lines in 22 files changed: 100 ins; 1094 del; 41 mod
  Patch: https://git.openjdk.java.net/jdk/pull/5039.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/5039/head:pull/5039

PR: https://git.openjdk.java.net/jdk/pull/5039