RFR: 8048269: Add flag to turn off class unloading after G1 concurrent mark

Stefan Karlsson stefan.karlsson at oracle.com
Mon Aug 4 14:07:06 UTC 2014


Hi all,

On 2014-07-18 00:14, Jon Masamitsu wrote:
>
> On 07/17/2014 12:25 AM, Thomas Schatzl wrote:
>> Hi,
>>
>> On Thu, 2014-07-17 at 08:38 +0200, Bengt Rutisson wrote:
>>> On 2014-07-17 07:02, Kirk Pepperdine wrote:
>>>>> I don't care for ClassUnloadingAfterConcurrentMark because turning it
>>>>> off makes me think that class unloading is going to occur "Before"
>>>>> concurrent mark.  How about
>>>>>
>>>>> ClassUnloadingWithConcurrentMark
>>>> +1
>>> I'm fine with this one too.
>> I would suggest ClassUnloadingAtConcurrentMark, because it seems more
>> concise, but either is okay.
>>
>> That would be similar to PrintHeapAtGC and so on. :)
>
> The flag sounds more concise but is it that correct?   With CMS
> at least (which we hope to make use this same flag) some
> of the reduction in work would be during marking but the
> freeing of the metaspace and the cleaning of the system
> dictionary come later (after the sweep).  I still like
> ClassUnloadingWithConcurrentMark - not as precise but
> maybe more correct?

I'm fine with this flag name.

Does anyone strongly oppose the flag name: ClassUnloadingWithConcurrentMark?

thanks,
StefanK

>
> Jon
>
>>
>> Thomas
>>
>>
>



More information about the hotspot-gc-dev mailing list