Re: [RFC] dma: passing "attributes" to dma_map_* routines

[Roland Dreier <rdreier@cisco.com>]

 > > Waaay back in October I sent some patches for passing additional 
 > > attributes to the dma_map_* routines:
 > > 
 > > http://marc.info/?l=linux-kernel&m=119137949604365&w=2
 > 
 > Do I understand correctly?:  A device and the CPUs communicate via two
 > separate memory areas:  A data buffer and a status FIFO.  The NUMA
 > interconnect may reorder accesses of the device to the areas.  (Write
 > accesses?  Read accesses?  Both?)

Yes, that is correct.  In-flight DMA writes from the device to system
memory can pass each other, so that the CPU sees a "complete" status
in the completion queue before the operation in question has actually
finished updating CPU memory.

 > To ensure synchronization between device and CPUs, you want to mark a
 > memory area which is to be dma-mapped with a flag which says:  "Writes
 > to the memory region will cause in-flight DMA to be flushed".  Whose
 > writes?  A write access from the device or a write access from a CPU?

Write access from the device.  The idea is to set the flag on the
completion queue, so that when the device writes the "complete" status
for the operation, all DMAs associated with that operation are flushed
first.

 - R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/