CRR (XXS): 7078465: G1: Don't use the undefined value (-1) for the G1 old memory pool max size

Tony Printezis tony.printezis at oracle.com
Thu Jan 12 15:51:07 UTC 2012


Hi all,

I'd like a couple of code reviews for this very small  change (one line!):

http://cr.openjdk.java.net/~tonyp/7078465/webrev.0/

Currently, all the G1 memory pools return "undefined" (-1) as their max 
size given that there are no hard boundaries between them. Jon Masamitsu 
suggested to at least return the heap max for the old memory pool so 
that the pool data is a little bit more informative.

Tony




More information about the hotspot-gc-dev mailing list