1. 14 9月, 2013 1 次提交
  2. 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
  3. 19 1月, 2011 1 次提交
    • T
      7011379: G1: overly long concurrent marking cycles · c1c48661
      tonyp 提交于
      Summary: This changeset introduces filtering of SATB buffers at the point when they are about to be enqueued. If this filtering clears enough entries on each buffer, the buffer can then be re-used and not enqueued. This cuts down the number of SATB buffers that need to be processed by the concurrent marking threads.
      Reviewed-by: johnc, ysr
      c1c48661
  4. 24 11月, 2010 1 次提交
  5. 02 10月, 2010 1 次提交
    • T
      6980838: G1: guarantee(false) failed: thread has an unexpected active value in its SATB queue · acd6a8e3
      tonyp 提交于
      Summary: Under certain circumstances a safepoint could happen between a JavaThread object being created and that object being added to the Java threads list. This could cause the active field of that thread's SATB queue to get out-of-sync with respect to the other Java threads. The solution is to activate the SATB queue, when necessary, before adding the thread to the Java threads list, not when the JavaThread object is created. The changeset also includes a small fix to rename the surrogate locker thread from "Surrogate Locker Thread (CMS)" to "Surrogate Locker Thread (Concurrent GC)" since it's also used in G1.
      Reviewed-by: iveresov, ysr, johnc, jcoomes
      acd6a8e3
  6. 28 5月, 2010 1 次提交
  7. 19 3月, 2010 1 次提交
    • T
      6935821: G1: threads created during marking do not active their SATB queues · 9677603a
      tonyp 提交于
      Summary: Newly-created threads always had the active field of their SATB queue initialized to false, even if they were created during marking. As a result, updates from threads created during a marking cycle were never enqueued and never processed. The fix includes remaining a method from active() to is_active() for readability and naming consistency.
      Reviewed-by: ysr, johnc
      9677603a
  8. 17 12月, 2009 1 次提交
    • I
      6862387: tune concurrent refinement further · 7f92f7a2
      iveresov 提交于
      Summary: Reworked the concurrent refinement: threads activation, feedback-based threshold adjustment, other miscellaneous fixes.
      Reviewed-by: apetrusenko, tonyp
      7f92f7a2
  9. 10 3月, 2009 1 次提交
    • X
      6814575: Update copyright year · 58e87f34
      xdono 提交于
      Summary: Update copyright for files that have been modified in 2009, up to 03/09
      Reviewed-by: katleman, tbell, ohair
      58e87f34
  10. 07 3月, 2009 1 次提交
  11. 10 2月, 2009 1 次提交
  12. 16 12月, 2008 1 次提交
    • X
      6785258: Update copyright year · f9cf0f22
      xdono 提交于
      Summary: Update copyright for files that have been modified starting July 2008 to Dec 2008
      Reviewed-by: katleman, ohair, tbell
      f9cf0f22
  13. 15 11月, 2008 1 次提交
    • I
      6770608: G1: Mutator thread can flush barrier and satb queues during safepoint · 5ee7f6f4
      iveresov 提交于
      6660573: G1: BigApps Failure : guarantee(satb_mq_set.completed_buffers_num() == 0,"invariant")
      Summary: When exiting a mutator thread is removed from the thread list before it has a chance to flush its SATB and barrier queues. If GC happens at this moment the objects that are refererred from these queues can be moved, which will case a crash. The fix is simply to flush the buffers before removing a thread from the list.
      Reviewed-by: jcoomes, tonyp
      5ee7f6f4
  14. 06 6月, 2008 1 次提交