comparison src/share/vm/gc_implementation/g1/g1CollectedHeap.hpp @ 1718:bb847e31b836

6974928: G1: sometimes humongous objects are allocated in young regions Summary: as the title says, sometimes we are allocating humongous objects in young regions and we shouldn't. Reviewed-by: ysr, johnc
author tonyp
date Tue, 17 Aug 2010 14:40:00 -0400
parents 5f429ee79634
children 8b10f48633dc
comparison
equal deleted inserted replaced
1717:688c3755d7af 1718:bb847e31b836
1030 // See CollectedHeap for semantics. 1030 // See CollectedHeap for semantics.
1031 1031
1032 virtual bool supports_tlab_allocation() const; 1032 virtual bool supports_tlab_allocation() const;
1033 virtual size_t tlab_capacity(Thread* thr) const; 1033 virtual size_t tlab_capacity(Thread* thr) const;
1034 virtual size_t unsafe_max_tlab_alloc(Thread* thr) const; 1034 virtual size_t unsafe_max_tlab_alloc(Thread* thr) const;
1035 virtual HeapWord* allocate_new_tlab(size_t size); 1035 virtual HeapWord* allocate_new_tlab(size_t word_size);
1036 1036
1037 // Can a compiler initialize a new object without store barriers? 1037 // Can a compiler initialize a new object without store barriers?
1038 // This permission only extends from the creation of a new object 1038 // This permission only extends from the creation of a new object
1039 // via a TLAB up to the first subsequent safepoint. If such permission 1039 // via a TLAB up to the first subsequent safepoint. If such permission
1040 // is granted for this heap type, the compiler promises to call 1040 // is granted for this heap type, the compiler promises to call