Shenandoah: reconsider heap region iterators memory ordering

XMLWordPrintable

    • gc
    • b11

      We use CASes to distributed workers between regions. Hotspot's default for atomic operations is memory_order_conservative, which emits two-way memory fences around the CASes at least on AArch64 and PPC64.

      This seems to be excessive for region distribution code, and "relaxed" is enough, since we don't piggyback memory ordering on these.

            Assignee:
            Aleksey Shipilev
            Reporter:
            Aleksey Shipilev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: