CodeHeap

[kirk.pepperdine at gmail.com]

Hi Tobias,

Thanks for the response. I’ve been lurking about watching the change as much as I could. The work it’s self is well done. It is the deviation from the naming convention that I was curious about. Are these segmented regions heaps? Or are these really just different segments of the code cache?

Regards,
Kirk

> On Mar 14, 2016, at 9:28 AM, Tobias Hartmann <tobias.hartmann at oracle.com> wrote:
> 
> Hi Kirk,
> 
> On 13.03.2016 23:08, kirk.pepperdine at gmail.com wrote:
>> Hi,
>> 
>> I’ve just been visiting the work done on the code cache and I’ve noticed that the pool names have been changed from CodeCache to CodeHeap. Is there any reason for the change to the naming convention?
>> 
>> Also, the DiagnosticCommand seems to refer to the compilerCodeCache as well as MemoryManager.CodeCacheManager which would seem inconsistent with this change.
> 
> With the Segmented Code Cache JEP [1], the code cache consists of multiple smaller segments (CodeHeaps) instead of one large segment. If segmentation is enabled (controlled by -XX:SegmentedCodeCache) we now have multiple pools corresponding to these individual code heaps.
> 
> Thanks,
> Tobias
> 
>> 
>> Regards,
>> Kirk
>> 
> 
> [1] https://bugs.openjdk.java.net/browse/JDK-8043304