On Sun, Jun 09, 2002 at 02:33:35AM -0400, Albert D. Cahalan wrote:
> For device --> memory DMA:
>
> 1. write back cache lines that cross unaligned boundries
What if some of the cache lines inside the DMA region are dirty and...
> 2. start the DMA
get evicted now when the CPU is doing something else?
> 3. invalidate the above cache lines
> 4. invalidate cache lines that are fully inside the DMA
You really need to:
1. write back cache lines that cross unaligned boundries
3. invalidate the above cache lines
2. start the DMA
4. invalidate cache lines that are fully inside the DMA
which is precisely we do on ARM.
> For memory --> device DMA:
>
> 1. write back all cache lines affected by the DMA
> 2. start the DMA
> 3. invalidate the above cache lines
What's the point of (3) ? The data in memory hasn't been changed by DMA.
What if we were writing out a page that was mmaped into a process, and
the process wrote to that page while we were DMAing ?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-
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/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:13 EST