[email protected] wrote:
> 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?)
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?
--
Stefan Richter
-=====-=-=== ==-- =--=-
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
