| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082683 | emb-9 | Kim Barrett | P4 | Resolved | Fixed | team |
| JDK-8086525 | 8u65 | Kim Barrett | P4 | Resolved | Fixed | b01 |
| JDK-8078853 | 8u60 | Kim Barrett | P4 | Resolved | Fixed | b17 |
| JDK-8137539 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
| JDK-8086141 | emb-8u60 | Kim Barrett | P4 | Resolved | Fixed | team |
SATBMarkQueueSet::apply_closure_to_completed_buffer() presently takes a worker_id index. It uses that to look up the closure associated with the worker by a preceding call to set_closure.
There is only one caller of this apply function, CMTask::drain_satb_buffers. It creates the desired closure, associates the closure with its worker id, and then calls apply_closure_to_completed_buffer.
We could eliminate set_closure and the underlying data structure, by simply having the apply_closure_xxx function take the closure as an argument rather than the worker id.
There is only one caller of this apply function, CMTask::drain_satb_buffers. It creates the desired closure, associates the closure with its worker id, and then calls apply_closure_to_completed_buffer.
We could eliminate set_closure and the underlying data structure, by simply having the apply_closure_xxx function take the closure as an argument rather than the worker id.
- backported by
-
JDK-8078853 SATB apply_closure_to_completed_buffer should have closure argument
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- blocks
-
JDK-8075215 SATB buffer processing found reclaimed humongous object
-
- Closed
-
(1 blocks)