RFR: 8226416: MonitorUsedDeflationThreshold can cause repeated async deflation requests [v6]

[Coleen Phillimore]

On Thu, 14 Jan 2021 01:12:18 GMT, Daniel D. Daugherty <dcubed at openjdk.org> wrote:

>> Adding support for a diagnostic option called NoAsyncDeflationProgressMax
>> with a default value of 3. If we have three async monitor deflation cycles in a
>> row with zero monitors deflated, then we adjust the in_use_list_ceiling up.
>> 
>> I've locally built and tested this fix on my MBP13 using the
>> MonitorUsedDeflationThresholdTest.java test that I wrote when this issue
>> first came up in June of 2019. I will be including this fix in my next Mach5
>> Tier[1-3] testing batch.
>
> Daniel D. Daugherty has updated the pull request incrementally with one additional commit since the last revision:
> 
>   address more dholmes CR comments.

LGTM.

test/hotspot/jtreg/runtime/Monitor/MonitorUsedDeflationThresholdTest.java line 30:

> 28: import java.io.InputStreamReader;
> 29: import java.util.regex.Pattern;
> 30: */

Why are these imports commented out?

-------------

Marked as reviewed by coleenp (Reviewer).

PR: https://git.openjdk.java.net/jdk/pull/1993