powerpc/powernv: Fix concurrency issue with npu->mmio_atsd_usage
authorReza Arbab <arbab@linux.ibm.com>
Fri, 3 Aug 2018 04:03:36 +0000 (23:03 -0500)
committerMichael Ellerman <mpe@ellerman.id.au>
Fri, 3 Aug 2018 10:09:01 +0000 (20:09 +1000)
We've encountered a performance issue when multiple processors stress
{get,put}_mmio_atsd_reg(). These functions contend for
mmio_atsd_usage, an unsigned long used as a bitmask.

The accesses to mmio_atsd_usage are done using test_and_set_bit_lock()
and clear_bit_unlock(). As implemented, both of these will require
a (successful) stwcx to that same cache line.

What we end up with is thread A, attempting to unlock, being slowed by
other threads repeatedly attempting to lock. A's stwcx instructions
fail and retry because the memory reservation is lost every time a
different thread beats it to the punch.

There may be a long-term way to fix this at a larger scale, but for
now resolve the immediate problem by gating our call to
test_and_set_bit_lock() with one to test_bit(), which is obviously
implemented without using a store.

Fixes: 1ab66d1fbada ("powerpc/powernv: Introduce address translation services for Nvlink2")
Signed-off-by: Reza Arbab <arbab@linux.ibm.com>
Acked-by: Alistair Popple <alistair@popple.id.au>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
arch/powerpc/platforms/powernv/npu-dma.c

index 4583153..8006c54 100644 (file)
@@ -440,8 +440,9 @@ static int get_mmio_atsd_reg(struct npu *npu)
        int i;
 
        for (i = 0; i < npu->mmio_atsd_count; i++) {
-               if (!test_and_set_bit_lock(i, &npu->mmio_atsd_usage))
-                       return i;
+               if (!test_bit(i, &npu->mmio_atsd_usage))
+                       if (!test_and_set_bit_lock(i, &npu->mmio_atsd_usage))
+                               return i;
        }
 
        return -ENOSPC;