Re: [Jikesrvm-researchers] JMTk heap sizes

[Steve B. <Ste...@an...>]

Sunil V. Soman wrote:
> Hi, are the EXTENT constants (LOS_SIZE, etc.) in the various plans the
> maximum amount of memory that a plan can address ? 
> 
> Why is it that the verbose:gc dump shows the same sizes for the various
> heaps for a plan (as given by the EXTENT constants), regardless of
> whatever 
> I pass in with the -X:h option? 
> 
> It is not clear how the -X:h flag is really used in jikesrvm
> 2.2.0. It used to be pretty straight-forward in version 2.1.1 (watson
> collectors).

I think you are confused.

-X:h sets the heap size, as expected, and as reflected in the output 
produced when the verbosity options are used.

I imagine you are looking at the *VIRTUAL MEMORY* set aside for various 
spaces (meta-data, generations, etc).  This is statically defined.

The things you ask about are described as "Memory layout constants" in 
comments immediately above their declaration.

Please read the code carefully.

--Steve