Fri, 08 Apr 2011 16:18:38 -0700 Merge
trims [Fri, 08 Apr 2011 16:18:38 -0700] rev 8933
Merge
Wed, 06 Apr 2011 16:02:53 -0700 Merge
jmasa [Wed, 06 Apr 2011 16:02:53 -0700] rev 8932
Merge
Fri, 18 Feb 2011 10:07:34 -0800 7020042: G1: Partially remove fix for 6994628
johnc [Fri, 18 Feb 2011 10:07:34 -0800] rev 8931
7020042: G1: Partially remove fix for 6994628 Summary: Disable reference discovery and processing during concurrent marking by disabling fix for 6994628. Reviewed-by: tonyp, ysr
Mon, 04 Apr 2011 14:23:17 -0400 7027766: G1: introduce flag to dump the liveness information per region at the end of marking
tonyp [Mon, 04 Apr 2011 14:23:17 -0400] rev 8930
7027766: G1: introduce flag to dump the liveness information per region at the end of marking Summary: Repurpose the existing flag G1PrintRegionLivenessInfo to print out the liveness distribution across the regions in the heap at the end of marking. Reviewed-by: iveresov, jwilhelm
Mon, 04 Apr 2011 13:18:35 -0400 7033292: G1: nightly failure: Non-dirty cards in region that should be dirty
tonyp [Mon, 04 Apr 2011 13:18:35 -0400] rev 8929
7033292: G1: nightly failure: Non-dirty cards in region that should be dirty Summary: The epochs on the card cache array are initialized to 0 and our initial epoch also starts at 0. So, until the first GC, it might be possible to successfully "claim" a card which was in fact never initialized. Reviewed-by: johnc, iveresov, ysr
Wed, 30 Mar 2011 10:26:59 -0400 7023069: G1: Introduce symmetric locking in the slow allocation path
tonyp [Wed, 30 Mar 2011 10:26:59 -0400] rev 8928
7023069: G1: Introduce symmetric locking in the slow allocation path 7023151: G1: refactor the code that operates on _cur_alloc_region to be re-used for allocs by the GC threads 7018286: G1: humongous allocation attempts should take the GC locker into account Summary: First, this change replaces the asymmetric locking scheme in the G1 slow alloc path by a summetric one. Second, it factors out the code that operates on _cur_alloc_region so that it can be re-used for allocations by the GC threads in the future. Reviewed-by: stefank, brutisso, johnc
Tue, 29 Mar 2011 22:36:16 -0400 7029458: G1: Add newly-reclaimed regions to the beginning of the region free list, not the end
tonyp [Tue, 29 Mar 2011 22:36:16 -0400] rev 8927
7029458: G1: Add newly-reclaimed regions to the beginning of the region free list, not the end Summary: What the synopsis says. Reviewed-by: jwilhelm, iveresov, johnc
Mon, 28 Mar 2011 10:58:54 -0700 7026932: G1: No need to abort VM when card count cache expansion fails
johnc [Mon, 28 Mar 2011 10:58:54 -0700] rev 8926
7026932: G1: No need to abort VM when card count cache expansion fails Summary: Manage allocation/freeing of the card cache counts and epochs arrays directly so that an allocation failure while attempting to expand these arrays does not abort the JVM. Failure to expand these arrays is not fatal. Reviewed-by: iveresov, tonyp
Wed, 23 Mar 2011 14:12:51 +0100 6948149: G1: Imbalance in termination times
brutisso [Wed, 23 Mar 2011 14:12:51 +0100] rev 8925
6948149: G1: Imbalance in termination times Summary: Changed default value of WorkStealingYieldsBeforeSleep from 1000 to 5000. Added more information to G1 pause logging. Reviewed-by: jwilhelm, tonyp, jmasa
Fri, 25 Mar 2011 17:39:20 -0700 Merge
jcoomes [Fri, 25 Mar 2011 17:39:20 -0700] rev 8924
Merge
Thu, 24 Mar 2011 15:47:01 -0700 7029036: Card-table verification hangs with all framework collectors, except G1, even before the first GC
ysr [Thu, 24 Mar 2011 15:47:01 -0700] rev 8923
7029036: Card-table verification hangs with all framework collectors, except G1, even before the first GC Summary: When verifying clean card ranges, use memory-range-bounded iteration over oops of objects overlapping that range, thus avoiding the otherwise quadratic worst-case cost of scanning large object arrays. Reviewed-by: jmasa, jwilhelm, tonyp
Thu, 24 Mar 2011 15:45:27 -0700 7030435: Some oop_oop_iterate_m() methods iterate outside of specified memory bounds
ysr [Thu, 24 Mar 2011 15:45:27 -0700] rev 8922
7030435: Some oop_oop_iterate_m() methods iterate outside of specified memory bounds Summary: Filter ref-containing locations through the memory-interval specified in the call. Reviewed-by: jcoomes, jwilhelm, tonyp
(0) -3000 -1000 -300 -100 -12 +12 +100 +300 +1000 +3000 +10000 +30000 tip