RFR (XS): 8188877: Improper synchronization in offer_termination

Andrew Haley aph at redhat.com
Wed Nov 29 10:24:09 UTC 2017

On 28/11/17 21:11, White, Derek wrote:
> Offer-termination just has a simple for-loop that delays some number of cycles. As high as 4k iterations * 140 cycles (per SpinPause() on x86), could be 573,000 cycles or so. For this case, especially where the termination test is a simple load, I think we should test _offered_termination in the spin-wait. This should have low overhead on the spinning thread and impose no impact on other threads.

Please point to the exact lines of code you're talking about.

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the hotspot-gc-dev mailing list