1. 08 12月, 2010 3 次提交
  2. 03 12月, 2010 1 次提交
  3. 02 12月, 2010 1 次提交
  4. 25 8月, 2010 1 次提交
    • T
      6974966: G1: unnecessary direct-to-old allocations · 41dac17c
      tonyp 提交于
      Summary: This change revamps the slow allocation path of G1. Improvements include the following: a) Allocations directly to old regions are now totally banned. G1 now only allows allocations out of young regions (with the only exception being humongous regions). b) The thread that allocates a new region (which is now guaranteed to be young) does not dirty all its cards. Each thread that successfully allocates out of a young region is now responsible for dirtying the cards that corresponding to the "block" that just got allocated. c) allocate_new_tlab() and mem_allocate() are now implemented differently and TLAB allocations are only done by allocate_new_tlab(). d) If a thread schedules an evacuation pause in order to satisfy an allocation request, it will perform the allocation at the end of the safepoint so that the thread that initiated the GC also gets "first pick" of any space made available by the GC. e) If a thread is unable to allocate a humongous object it will schedule an evacuation pause in case it reclaims enough regions so that the humongous allocation can be satisfied aftewards. f) The G1 policy is more careful to set the young list target length to be the survivor number +1. g) Lots of code tidy up, removal, refactoring to make future changes easier.
      Reviewed-by: johnc, ysr
      41dac17c
  5. 24 11月, 2010 2 次提交
  6. 23 11月, 2010 1 次提交
  7. 20 11月, 2010 3 次提交
    • C
      Merge · b76f4992
      coleenp 提交于
      b76f4992
    • I
      Merge · 22d4b2a0
      iveresov 提交于
      22d4b2a0
    • J
      Merge · 81937723
      jmasa 提交于
      81937723
  8. 19 11月, 2010 3 次提交
  9. 17 11月, 2010 5 次提交
    • Z
      Merge · ac1033dc
      zgu 提交于
      ac1033dc
    • J
      Merge · 0baf2379
      johnc 提交于
      0baf2379
    • I
      7000349: Tiered reacts incorrectly to C1 compilation failures · a9d5455e
      iveresov 提交于
      Summary: Fix policy reaction to C1 comilation failures, make C1 properly report errors.
      Reviewed-by: kvn
      a9d5455e
    • J
      6978187: G1: assert(ParallelGCThreads> 1 || n_yielded() == _hrrs->occupied()) strikes again · 8d02802f
      johnc 提交于
      Summary: An evacuation failure while copying the roots caused an object, A, to be forwarded to itself. During the subsequent RSet updating a reference to A was processed causing the reference to be added to the RSet of A's heap region. As a result of adding to the remembered set we ran into the issue described in 6930581 - the sparse table expanded and the RSet scanning code walked the cards in one instance of RHashTable (_cur) while the occupied() counts the cards in the expanded table (_next).
      Reviewed-by: tonyp, iveresov
      8d02802f
    • Y
      7000578: CMS: assert(SafepointSynchronize::is_at_safepoint()) failed: Else races are possible · 3e22a1c3
      ysr 提交于
      Summary: Weakened assert in onj_is_alive() to allow its use at initialization time when is_at_safepoint() normally reports false; added some related asserts to check order of is_init_completed() after Universe::is_fully_initialized().
      Reviewed-by: jcoomes
      3e22a1c3
  10. 16 11月, 2010 1 次提交
    • J
      Merge · 1cb7ed62
      jmasa 提交于
      1cb7ed62
  11. 13 11月, 2010 1 次提交
  12. 12 11月, 2010 7 次提交
  13. 11 11月, 2010 2 次提交
    • T
      Merge · 6a5287b9
      trims 提交于
      6a5287b9
    • T
      Merge · d3be82dc
      trims 提交于
      d3be82dc
  14. 10 11月, 2010 3 次提交
  15. 09 11月, 2010 1 次提交
  16. 07 11月, 2010 2 次提交
  17. 06 11月, 2010 3 次提交
    • I
      Merge · 99a453d9
      iveresov 提交于
      99a453d9
    • I
      6997456: Not possible to build just compiler2 · ddf554aa
      iveresov 提交于
      Summary: Fix the compiler error. Allow to build just c2 specifying FORCE_TIERED=0 on the command line.
      Reviewed-by: never, kvn
      ddf554aa
    • Y
      6997298: fatal error: must own lock CMS_markBitMap_lock during heap dump · 385dacb7
      ysr 提交于
      Summary: Since we are at a stop-world pause, the existing CMS-phase checks are sufficient for safety, and the locking check can be safely elided. Elaborated documentation comment to the case where class unloading and verification are disabled, and the query happens when we aren't in the sweeping phase, where the answer "false" would be (almost everywhere) too pessimistic.
      Reviewed-by: jmasa, johnc, tonyp
      385dacb7