mirror of
https://github.com/openjdk/jdk.git
synced 2026-03-28 08:39:56 +00:00
8346737: GenShen: Generational memory pools should not report zero for maximum capacity
Reviewed-by: kdnilsen, ysr Backport-of: 249f141211c94afcce70d9d536d84e108e07b4e5
This commit is contained in:
parent
7d4fa7818b
commit
ff9b8e4607
@ -93,11 +93,6 @@ size_t ShenandoahGenerationalMemoryPool::used_in_bytes() {
|
||||
return _generation->used();
|
||||
}
|
||||
|
||||
size_t ShenandoahGenerationalMemoryPool::max_size() const {
|
||||
return _generation->max_capacity();
|
||||
}
|
||||
|
||||
|
||||
ShenandoahYoungGenMemoryPool::ShenandoahYoungGenMemoryPool(ShenandoahHeap* heap) :
|
||||
ShenandoahGenerationalMemoryPool(heap,
|
||||
"Shenandoah Young Gen",
|
||||
|
||||
@ -55,7 +55,6 @@ public:
|
||||
explicit ShenandoahGenerationalMemoryPool(ShenandoahHeap* heap, const char* name, ShenandoahGeneration* generation);
|
||||
MemoryUsage get_memory_usage() override;
|
||||
size_t used_in_bytes() override;
|
||||
size_t max_size() const override;
|
||||
};
|
||||
|
||||
class ShenandoahYoungGenMemoryPool : public ShenandoahGenerationalMemoryPool {
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user