On Tue, Mar 27, 2018 at 2:35 PM, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> wrote: > On Tue, 2018-03-27 at 10:46 -0400, Sinan Kaya wrote: >> combined buffers. >> >> Alex: >> "Don't bother. I can tell you right now that for x86 you have to have a >> wmb() before the writel(). > > No, this isn't the semantics of writel. You shouldn't need it unless > something changed and we need to revisit our complete understanding of > *all* MMIO accessor semantics. The issue seems to be that there have been two different ways of dealing with this. There has historically been a number of different drivers that have been carrying this wmb() workaround since something like 2002. I get that the semantics for writel might have changed since then, but those of us who already have the wmb() in our drivers will be very wary of anyone wanting to go through and remove them since writel is supposed to be "good enough". I would much rather err on the side of caution here. I view the wmb() + writel_relaxed() as more of a driver owning and handling this itself. Besides in the Intel Ethernet driver case it is better performance as our wmb() placement for us also provides a secondary barrier so we don't need to add a separate smp_wmb() to deal with a potential race we have with the Tx cleanup. > At least for UC space, it has always been accepted (and enforced) that > writel would not require any other barrier to order vs. previous stores > to memory. So the one thing I would question here is if this is UC vs UC or if this extends to other types as well? So for x86 we could find references to Write Combining being flushed by a write to UC memory, however I have yet to find a clear explanation of what a write to UC does to WB. My personal inclination would be to err on the side of caution. I just don't want us going through and removing the wmb() calls because it "should" work. I would want to know for certain it will work. - Alex -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
