RFR: 8226416: MonitorUsedDeflationThreshold can cause repeated async deflation requests

[Daniel D.Daugherty]

On Thu, 7 Jan 2021 23:15:57 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.
>
> Note: I'm testing out stacking patches in Git so there are commits for
> https://bugs.openjdk.java.net/browse/JDK-8259397 and
> https://bugs.openjdk.java.net/browse/JDK-8259349 that show up in this PR.
> 
> This is the correct commit for this PR review: https://github.com/openjdk/jdk/commit/af5c3fec96d1d45af5881947d366e22cb8962dc3

I was hoping that each subsequent PR would be baselined on the previous
branch so that each PR would only have a single commit in it. It didn't work
out that way so that's why I included this blurb in a comment:

> This is the correct commit for this PR review: https://github.com/openjdk/jdk/commit/af5c3fec96d1d45af5881947d366e22cb8962dc3

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

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