On Fri, 2010-08-06 at 04:43 -0700, Rui Machado wrote: > Hi there, > > > There are two kinds supported. QLogic's driver does them in > > the host driver so they are atomic with respect to all the CPUs > > in the host. Mellanox uses HCA wide atomic which means the > > HCA will do a memory read/write without allowing other reads > > or writes from different QP operations passing through that > > HCA to get in between. The CPUs on the host won't see > > atomic operations since from their perspective, it looks > > like a normal read and write from the PCIe bus. > > So if the CPU writes/reads to/from the same address, even atomically > (lock), there might be room for some inconsistency on the values? It > is not really atomic from the whole system point of view, just for the > HCA? If so, is there any possibility to make the whole operation > 'system-wide' atomic?
Correct. It won't be consistent from the HCA's point of view if other HCAs or CPUs are modifying the memory - even if they do it atomically. It is only consistent if a single HCA is doing atomic ops to the memory. There is no possibility to change this unless PCIe atomic operations are used by the HCA and if the root complex supports atomic operations. I don't know of any HCAs or root complex chips which have this support yet. > > You can see what type the HCA supports with "ibv_devinfo -v" > > and look for "atomic_cap: ATOMIC_HCA (1)" or > > "atomic_cap: ATOMIC_GLOB (2)". > > ATOMIC_HCA (1) is what I see in my Mellanox hardware. This is the case > you mentioned, "without allowing other reads or writes from different > QP operations passing through that HCA to get in between" > ATOMIC_GLOB (2) means with respect to all HCAs and even the CPU? Correct. > Cheers, > Rui > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
