1. 19 11月, 2011 1 次提交
  2. 21 11月, 2011 1 次提交
  3. 19 11月, 2011 1 次提交
  4. 08 11月, 2011 2 次提交
  5. 02 11月, 2011 1 次提交
  6. 27 10月, 2011 1 次提交
  7. 26 10月, 2011 2 次提交
  8. 24 10月, 2011 1 次提交
    • J
      7096030: G1: PrintGCDetails enhancements · 15519f74
      johnc 提交于
      7102445: G1: Unnecessary Resource allocations during RSet scanning
      Summary: Add a new per-worker thread line in the PrintGCDetails output. GC Worker Other is the difference between the elapsed time for the parallel phase of the evacuation pause and the sum of the times of the sub-phases (external root scanning, mark stack scanning, RSet updating, RSet scanning, object copying, and termination) for that worker. During RSet scanning, stack allocate DirtyCardToOopClosure objects; allocating these in a resource area was causing abnormally high GC Worker Other times while the worker thread freed ResourceArea chunks.
      Reviewed-by: tonyp, jwilhelm, brutisso
      15519f74
  9. 21 10月, 2011 1 次提交
    • J
      7099824: G1: we should take the pending list lock before doing the remark pause · 08630d11
      johnc 提交于
      Summary: Acquire the pending list lock in the prologue method of G1's concurrent VM_Operation and release the lock in the epilogue() method. The locking/unlocking order of the pending list lock and the Heap_lock should match that in the prologue and epilogue methods of VM_GC_Operation.
      Reviewed-by: tonyp, ysr
      08630d11
  10. 20 10月, 2011 1 次提交
  11. 18 10月, 2011 1 次提交
  12. 14 10月, 2011 3 次提交
  13. 07 10月, 2011 1 次提交
    • Y
      7095236: G1: _markedRegions never contains NULL regions · 4fe35e43
      ysr 提交于
      Summary: Removed the code for skipping over NULL regions in _markedRegions, replacing it with an assertion that a NULL region is never encountered; removed dead methods, remove() and remove_region(), and inlined a simplified addRegion() directly into fillCache().
      Reviewed-by: brutisso, tonyp
      4fe35e43
  14. 05 10月, 2011 1 次提交
  15. 28 9月, 2011 1 次提交
  16. 26 9月, 2011 1 次提交
  17. 14 9月, 2011 1 次提交
  18. 12 9月, 2011 1 次提交
  19. 04 10月, 2011 2 次提交
  20. 29 9月, 2011 1 次提交
    • J
      7086533: G1: assert(!_g1->is_obj_dead(obj)): We should not be preserving dead... · c908a927
      johnc 提交于
      7086533: G1: assert(!_g1->is_obj_dead(obj)): We should not be preserving dead objs: g1CollectedHeap.cpp:3835
      Summary: Some objects may not be marked in the event of an evacuation failure in a partially young GC, during a marking cycle. Avoid this situation by not allowing partially young GCs during a marking cycle.
      Reviewed-by: tonyp, ysr, brutisso
      c908a927
  21. 24 9月, 2011 1 次提交
  22. 23 9月, 2011 1 次提交
    • J
      6484982: G1: process references during evacuation pauses · 9c3adbcc
      johnc 提交于
      Summary: G1 now uses two reference processors - one is used by concurrent marking and the other is used by STW GCs (both full and incremental evacuation pauses). In an evacuation pause, the reference processor is embedded into the closures used to scan objects. Doing so causes causes reference objects to be 'discovered' by the reference processor. At the end of the evacuation pause, these discovered reference objects are processed - preserving (and copying) referent objects (and their reachable graphs) as appropriate.
      Reviewed-by: ysr, jwilhelm, brutisso, stefank, tonyp
      9c3adbcc
  23. 22 9月, 2011 4 次提交
  24. 21 9月, 2011 1 次提交
    • J
      7092412: G1: Some roots not marked during an initial mark that gets an evacuation failure · 279b083d
      johnc 提交于
      Summary: As a result of the changes for 7080389, an evacuation failure during an initial mark pause may result in some root objects not being marked. Pass whether the caller is a root scanning closure into the evacuation failure handling code so that the thread that successfully forwards an object to itself also marks the object.
      Reviewed-by: ysr, brutisso, tonyp
      279b083d
  25. 20 9月, 2011 1 次提交
    • T
      7059019: G1: add G1 support to the SA · 29a35788
      tonyp 提交于
      Summary: Extend the SA to recognize the G1CollectedHeap and implement any code that's needed by our serviceability tools (jmap, jinfo, jstack, etc.) that depend on the SA.
      Reviewed-by: never, poonam, johnc
      29a35788
  26. 09 9月, 2011 1 次提交
  27. 08 9月, 2011 3 次提交
    • B
      6929868: G1: introduce min / max young gen size bounds · 499845d6
      brutisso 提交于
      Summary: Make G1 handle young gen size command line flags more consistently
      Reviewed-by: tonyp, jwilhelm
      499845d6
    • T
      7084509: G1: fix inconsistencies and mistakes in the young list target length calculations · 389cad56
      tonyp 提交于
      Summary: Fixed inconsistencies and mistakes in the young list target length calculations so that a) the calculated target length is optimal (before, it was not), b) other parameters like max survivor size and max gc locker eden expansion are always consistent with the calculated target length (before, they were not always), and c) the resulting target length was always bound by desired min and max values (before, it was not).
      Reviewed-by: brutisso, johnc
      389cad56
    • T
      7050392: G1: Introduce flag to generate a log of the G1 ergonomic decisions · e4a3f7b0
      tonyp 提交于
      Summary: It introduces ergonomic decision logging in G1 for the following heuristics: heap sizing, collection set construction, concurrent cycle initiation, and partially-young GC start/end. The code has a bit of refactoring in a few places to make the decision logging possible. It also replaces alternative ad-hoc logging that we have under different parameters and switches (G1_DEBUG, G1PolicyVerbose).
      Reviewed-by: johnc, ysr
      e4a3f7b0
  28. 01 9月, 2011 2 次提交
  29. 30 8月, 2011 1 次提交