JDK-6949254 : G1: Introduce framework for concurrent operations in G1
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs18
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2010-05-03
  • Updated: 2019-02-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
Description
In G1 we tend to want to perform some operations concurrently to take them off the STW pauses. Such operations include:

1) reclaim regions found to be empty during cleanup (current)
2) sample RSet length of young regions (current)
3) reclaim collection set regions (future, see 6868854)

Right now, the way we do such operations is ad-hoc (1 is done piggy-backed on the main concurrent marking thread, 2 is done piggy-backed on the concurrent refinement threads). It'd be helpful to have a framework to be able to easily schedule concurrent operations in G1 to deal with such operations in a uniform manner.