Hi Alex, On Thu, Nov 13, 2014 at 07:27:23PM +0000, Alexander Duyck wrote: > It is common for device drivers to make use of acquire/release semantics > when dealing with descriptors stored in device memory. On reviewing the > documentation and code for smp_load_acquire() and smp_store_release() as > well as reviewing an IBM website that goes over the use of PowerPC barriers > at http://www.ibm.com/developerworks/systems/articles/powerpc.html it > occurred to me that the same code could likely be applied to device drivers. > > As a result this patch introduces load_acquire() and store_release(). The > load_acquire() function can be used in the place of situations where a test > for ownership must be followed by a memory barrier. The below example is > from ixgbe: > > if (!rx_desc->wb.upper.status_error) > break; > > /* This memory barrier is needed to keep us from reading > * any other fields out of the rx_desc until we know the > * descriptor has been written back > */ > rmb(); > > With load_acquire() this can be changed to: > > if (!load_acquire(&rx_desc->wb.upper.status_error)) > break; I still don't think this is a good idea for the specific use-case you're highlighting. On ARM, an mb() can be *significantly* more expensive than an rmb() (since we may have to drain store buffers on an outer L2 cache) and on arm64 it's not at all clear that an LDAR is more efficient than an LDR; DMB LD sequence. I can certainly imagine implementations where the latter would be preferred. So, whilst I'm perfectly fine to go along with mandatory acquire/release macros (we should probably add a check to barf on __iomem pointers), I don't agree with using them in preference to finer-grained read/write barriers. Doing so will have a real impact on I/O performance. Finally, do you know of any architectures where load_acquire/store_release aren't implemented the same way as the smp_* variants on SMP kernels? Will -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
