On Mon, Mar 14, 2016 at 05:23:44PM -0400, Matthew Wilcox wrote: > On Mon, Mar 14, 2016 at 12:14:37PM -0600, Stephen Bates wrote: > > 3. Coherency Issues. When IOMEM is written from both the CPU and a PCIe > > peer there is potential for coherency issues and for writes to occur out > > of order. This is something that users of this feature need to be > > cognizant of and may necessitate the use of CONFIG_EXPERT. Though really, > > this isn't much different than the existing situation with RDMA: if > > userspace sets up an MR for remote use, they need to be careful about > > using that memory region themselves. > > There's more to the coherency problem than this. As I understand it, on > x86, memory in a PCI BAR does not participate in the coherency protocol. > So you can get a situation where CPU A stores 4 bytes to offset 8 in a > cacheline, then CPU B stores 4 bytes to offset 16 in the same cacheline, > and CPU A's write mysteriously goes missing. No, this cannot happen with writing combining. You need full caching turned on to get that kind of problem. write combining can only combine writes, it cannot make up writes that never existed. That said, I question I don't know the answer to, is how does write locking/memory barries interact with the write combining CPU buffers, and are all the fencing semantics guarenteed.. There is some interaction there (some drivers use write combining a lot).. but that sure is a rarely used corner area... The other issue is that the fencing mechanism RDMA uses to create ordering with system memory is not good enough to fence peer-peer transactions in the general case. It is only possibly good enough if all the transactions run through the root complex. > I may have misunderstood the exact details when this was explained to me a > few years ago, but the details were horrible enough to run away screaming. > Pretending PCI BARs are real memory? Just Say No. Someone should probably explain in more detail what this is even good for, DAX on PCI-E bar memory seems goofy in the general case. I was under the impression the main use case involved the CPU never touching these memories and just using them to route-through to another IO device (eg network). So all these discussions about CPU coherency seem a bit strange. Jason -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>