1. 17 9月, 2012 1 次提交
  2. 02 9月, 2012 1 次提交
  3. 29 8月, 2012 1 次提交
    • J
      7041879: G1: introduce stress testing parameter to cause frequent evacuation failures · 3c3c2c12
      johnc 提交于
      Summary: Add the flags G1EvacuationFailureALot flag (and supporting flags) to force trigger evacuation failures. The support flags control how often to trigger an evacuation failure and during which types of evacuation pause. This functionality is analogous to that of PromotionFailureALot for the other collectors.
      Reviewed-by: brutisso
      3c3c2c12
  4. 23 8月, 2012 1 次提交
  5. 22 8月, 2012 2 次提交
    • J
      7185699: G1: Prediction model discrepancies · 4e8955cf
      johnc 提交于
      Summary: Correct the result value of G1CollectedHeap::pending_card_num(). Change the code that calculates the GC efficiency of a non-young heap region to use historical data from mixed GCs and the actual number of live bytes when predicting how long it would take to collect the region. Changes were also reviewed by Thomas Schatzl.
      Reviewed-by: azeemj, brutisso
      4e8955cf
    • J
      7192128: G1: Extend fix for 6948537 to G1's BOT · ddfab1b9
      johnc 提交于
      Summary: G1 does not appear to be immune to the issue described in CR 6948537 and increasing the size of old-generation PLABs appears to increase the liklihood of seeing the issue. Extend the fix for 6948537 to G1's BlockOffsetTable.
      Reviewed-by: brutisso, jmasa
      ddfab1b9
  6. 07 8月, 2012 1 次提交
  7. 20 7月, 2012 1 次提交
  8. 12 7月, 2012 1 次提交
  9. 29 6月, 2012 1 次提交
    • Z
      6995781: Native Memory Tracking (Phase 1) · bdfb3cf5
      zgu 提交于
      7151532: DCmd for hotspot native memory tracking
      Summary: Implementation of native memory tracking phase 1, which tracks VM native memory usage, and related DCmd
      Reviewed-by: acorn, coleenp, fparain
      bdfb3cf5
  10. 26 6月, 2012 1 次提交
  11. 04 6月, 2012 1 次提交
  12. 06 6月, 2012 1 次提交
  13. 01 6月, 2012 1 次提交
  14. 30 5月, 2012 1 次提交
    • J
      7143858: G1: Back to back young GCs with the second GC having a minimally sized eden · 893ceddc
      johnc 提交于
      Summary: Before the last thread to leave a JNI critical region was able to schedule a GCLocker Initiated GC, another thread was attempting an allocation and saw that the GCLocker region was no longer active and successfully scheduled a GC. Stall allocating threads until the GCLocker Initiated GC is performed and then retry the allocation.
      Reviewed-by: brutisso, huntch
      893ceddc
  15. 15 5月, 2012 1 次提交
  16. 14 5月, 2012 1 次提交
    • B
      7161545: G1: Minor cleanups to the G1 logging · 3c2bae90
      brutisso 提交于
      Summary: Rename "to-space-overflow" to "to-space-exhausted", Introduce one decimal point in the size format, Add Sum to the aggregate and re-order the entries, Add number of GC workers to the log output
      Reviewed-by: johnc, jwilhelm
      3c2bae90
  17. 25 4月, 2012 1 次提交
  18. 26 4月, 2012 1 次提交
    • J
      7143490: G1: Remove HeapRegion::_top_at_conc_mark_count · 7b83234d
      johnc 提交于
      Summary: Removed the HeapRegion::_top_at_conc_mark_count field. It is no longer needed as a result of the changes for 6888336 and 7127706. Refactored the closures that finalize and verify the liveness counting data so that common functionality was placed into a base class.
      Reviewed-by: brutisso, tonyp
      7b83234d
  19. 19 4月, 2012 1 次提交
    • T
      7145441: G1: collection set chooser-related cleanup · 0c52c8e5
      tonyp 提交于
      Summary: Cleanup of the CSet chooser class: standardize on uints for region num and indexes (instead of int, jint, etc.), make the method / field naming style more consistent, remove a lot of dead code.
      Reviewed-by: johnc, brutisso
      0c52c8e5
  20. 18 4月, 2012 1 次提交
  21. 16 4月, 2012 1 次提交
  22. 13 4月, 2012 1 次提交
    • B
      7160728: Introduce an extra logging level for G1 logging · dd643c7f
      brutisso 提交于
      Summary: Added log levels "fine", "finer" and "finest". Let PrintGC map to "fine" and PrintGCDetails map to "finer". Separated out the per worker information in the G1 logging to the "finest" level.
      Reviewed-by: stefank, jwilhelm, tonyp, johnc
      dd643c7f
  23. 16 3月, 2012 1 次提交
  24. 14 3月, 2012 1 次提交
    • J
      7143511: G1: Another instance of high GC Worker Other time (50ms) · 26afc937
      johnc 提交于
      Summary: Tiered compilation has increased the number of nmethods in the code cache. This has, in turn, significantly increased the number of marked nmethods processed during the StrongRootsScope destructor. Create a specialized version of CodeBlobToOopClosure for G1 which places only those nmethods that contain pointers into the collection set on to the marked nmethods list.
      Reviewed-by: iveresov, tonyp
      26afc937
  25. 13 3月, 2012 1 次提交
    • J
      7147724: G1: hang in SurrogateLockerThread::manipulatePLL · f0980866
      johnc 提交于
      Summary: Attempting to initiate a marking cycle when allocating a humongous object can, if a marking cycle is successfully initiated by another thread, result in the allocating thread spinning until the marking cycle is complete. Eliminate a deadlock between the main ConcurrentMarkThread, the SurrogateLocker thread, the VM thread, and a mutator thread waiting on the SecondaryFreeList_lock (while free regions are going to become available) by not manipulating the pending list lock during the prologue and epilogue of the cleanup pause.
      Reviewed-by: brutisso, jcoomes, tonyp
      f0980866
  26. 16 2月, 2012 1 次提交
    • T
      7132029: G1: mixed GC phase lasts for longer than it should · 33a49849
      tonyp 提交于
      Summary: Revamp of the mechanism that chooses old regions for inclusion in the CSet. It simplifies the code and introduces min and max bounds on the number of old regions added to the CSet at each mixed GC to avoid pathological cases. It also ensures that when we do a mixed GC we'll always find old regions to add to the CSet (i.e., it eliminates the case where a mixed GC will collect no old regions which can happen today).
      Reviewed-by: johnc, brutisso
      33a49849
  27. 01 2月, 2012 1 次提交
  28. 26 1月, 2012 1 次提交
    • T
      7127706: G1: re-enable survivors during the initial-mark pause · b73e0e37
      tonyp 提交于
      Summary: Re-enable survivors during the initial-mark pause. Afterwards, the concurrent marking threads have to scan them and mark everything reachable from them. The next GC will have to wait for the survivors to be scanned.
      Reviewed-by: brutisso, johnc
      b73e0e37
  29. 14 2月, 2012 1 次提交
  30. 12 1月, 2012 1 次提交
    • J
      6484965: G1: piggy-back liveness accounting phase on marking · f13c0dfe
      johnc 提交于
      Summary: Remove the separate counting phase of concurrent marking by tracking the amount of marked bytes and the cards spanned by marked objects in marking task/worker thread local data structures, which are updated as individual objects are marked.
      Reviewed-by: brutisso, tonyp
      f13c0dfe
  31. 24 1月, 2012 1 次提交
    • B
      7132311: G1: assert((s == klass->oop_size(this)) ||... · 7864cfc8
      brutisso 提交于
      7132311: G1: assert((s == klass->oop_size(this)) || (Universe::heap()->is_gc_active() && ((is_typeArray()...
      Summary: Move the check for when to call collect() to before we do a humongous object allocation
      Reviewed-by: stefank, tonyp
      7864cfc8
  32. 21 1月, 2012 1 次提交
  33. 18 1月, 2012 1 次提交
  34. 17 1月, 2012 1 次提交
  35. 11 1月, 2012 1 次提交
    • T
      6888336: G1: avoid explicitly marking and pushing objects in survivor spaces · a6a74fef
      tonyp 提交于
      Summary: This change simplifies the interaction between GC and concurrent marking. By disabling survivor spaces during the initial-mark pause we don't need to propagate marks of objects we copy during each GC (since we never need to copy an explicitly marked object).
      Reviewed-by: johnc, brutisso
      a6a74fef
  36. 10 1月, 2012 1 次提交
  37. 07 1月, 2012 1 次提交
  38. 24 12月, 2011 1 次提交
  39. 05 1月, 2012 1 次提交
    • T
      7113006: G1: excessive ergo output when an evac failure happens · c182ec48
      tonyp 提交于
      Summary: Introduce a flag that is set when a heap expansion attempt during a GC fails so that we do not consantly attempt to expand the heap when it's going to fail anyway. This not only prevents the excessive ergo output (which is generated when a region allocation fails) but also avoids excessive and ultimately unsuccessful expansion attempts.
      Reviewed-by: jmasa, johnc
      c182ec48