JDK-8149331 : Re-examine G1 use of os::processor_count
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Other
  • Submitted: 2016-02-08
  • Updated: 2016-07-21
  • Resolved: 2016-07-21
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.
JDK 9
9Resolved
Related Reports
Relates :  
JDK-8147910 - Cache initial active_processor_count
Description
The change applied in sub-task JDK-8147906 was backed out because the G1 code seems to depend upon the value for the number of processors not changing. So the use of processor_count needs to be re-examined to determine exactly what the expectations are. It may be that G1 needs the proposed initial_active_processor_count API - see JDK-8147910.
Comments
This is a sub-task of another change about examining the current code. There is no expected resulting code.
21-07-2016
G1 needs the proposed initial_active_processor_count API, otherwise it may crash at startup. See also the proposed patch there.
21-07-2016