src/share/vm/gc_implementation/g1/g1CollectorPolicy.hpp

rev 3905 : 8001424: G1: Rename certain G1-specific flags
Summary: Rename G1DefaultMinNewGenPercent, G1DefaultMaxNewGenPercent, and G1OldCSetRegionLiveThresholdPercent to G1NewSizePercent, G1MaxNewSizePercent, and G1MixedGCLiveThresholdPercent respectively. Continue, however, to accept the previous names. If both are specified, the new name takes precedence.
Reviewed-by:

*** 92,113 ****
  // size. Also, these are general options taking byte sizes. G1 will
  // internally work with a number of regions instead. So, some rounding
  // will occur.
  //
  // If nothing related to the the young gen size is set on the command
! // line we should allow the young gen to be between
! // G1DefaultMinNewGenPercent and G1DefaultMaxNewGenPercent of the
! // heap size. This means that every time the heap size changes the
! // limits for the young gen size will be updated.
  //
  // If only -XX:NewSize is set we should use the specified value as the
! // minimum size for young gen. Still using G1DefaultMaxNewGenPercent
! // of the heap as maximum.
  //
  // If only -XX:MaxNewSize is set we should use the specified value as the
! // maximum size for young gen. Still using G1DefaultMinNewGenPercent
! // of the heap as minimum.
  //
  // If -XX:NewSize and -XX:MaxNewSize are both specified we use these values.
  // No updates when the heap size changes. There is a special case when
  // NewSize==MaxNewSize. This is interpreted as "fixed" and will use a
  // different heuristic for calculating the collection set when we do mixed
--- 92,113 ----
  // size. Also, these are general options taking byte sizes. G1 will
  // internally work with a number of regions instead. So, some rounding
  // will occur.
  //
  // If nothing related to the the young gen size is set on the command
! // line we should allow the young gen to be between G1NewSizePercent
! // and G1MaxNewSizePercent of the heap size. This means that every time
! // the heap size changes, the limits for the young gen size will be
! // recalculated.
  //
  // If only -XX:NewSize is set we should use the specified value as the
! // minimum size for young gen. Still using G1MaxNewSizePercent of the
! // heap as maximum.
  //
  // If only -XX:MaxNewSize is set we should use the specified value as the
! // maximum size for young gen. Still using G1NewSizePercent of the heap
! // as minimum.
  //
  // If -XX:NewSize and -XX:MaxNewSize are both specified we use these values.
  // No updates when the heap size changes. There is a special case when
  // NewSize==MaxNewSize. This is interpreted as "fixed" and will use a
  // different heuristic for calculating the collection set when we do mixed