United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6864886 G1: rename -XX parameters related to update buffers
JDK-6864886 : G1: rename -XX parameters related to update buffers

Details
Type:
Enhancement
Submit Date:
2009-07-24
Status:
Resolved
Updated Date:
2010-04-04
Project Name:
JDK
Resolved Date:
2009-08-22
Component:
hotspot
OS:
generic
Sub-Component:
gc
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
hs16
Fixed Versions:
hs16 (b08)

Related Reports
Backport:
Backport:

Sub Tasks

Description
From an e-mail I recently sent:

I noticed that some G1 parameters are very badly (and inconsistently) named!

In g1_globals.hpp:

1) G1DirtyCardQueueMax - maximum update buffer queue length before mutators start processing update buffers

In globals.hpp:

2) DCQBarrierQueueBufferSize - length (it's not really size) of the update buffers
3) DCQBarrierProcessCompletedThreshold - how many update buffers must be in the queue before concurrent refinement threads start processing them

First, given that 2) and 3) are only used by G1, I think they should get the G1 prefix (and be moved to the g1_globals.hpp file). Second, I'd like to make the parameter names more consistent. These are the proposed new names:

1) G1UpdateBufferQueueMaxLength
2) G1UpdateBufferLength
3) G1UpdateBufferQueueProcessingThreshold

                                    

Comments
EVALUATION

See Description.
                                     
2009-07-24
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/27f6a9b9c311
                                     
2009-07-29
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/27f6a9b9c311
                                     
2009-07-31



Hardware and Software, Engineered to Work Together