Re: refactor dma_cache_sync V2

2017-10-19 Thread Christoph Hellwig
On Mon, Oct 16, 2017 at 02:44:42PM +0200, Christoph Hellwig wrote: > On Tue, Oct 03, 2017 at 12:49:51PM +0100, Robin Murphy wrote: > > Reviewed-by: Robin Murphy > > Thanks Robin. I've heard very little from the arch maintainers, > but if people remain silent I will apply the whole series to the

Re: refactor dma_cache_sync V2

2017-10-16 Thread Christoph Hellwig
On Tue, Oct 03, 2017 at 12:49:51PM +0100, Robin Murphy wrote: > Reviewed-by: Robin Murphy Thanks Robin. I've heard very little from the arch maintainers, but if people remain silent I will apply the whole series to the dma-mapping tree in the next days. __

Re: refactor dma_cache_sync V2

2017-10-03 Thread Robin Murphy
On 03/10/17 11:43, Christoph Hellwig wrote: > The dma_cache_sync routines is used to flush caches for memory returned > by dma_alloc_attrs with the DMA_ATTR_NON_CONSISTENT flag (or previously > from dma_alloc_noncoherent), but the requirements for it seems to be > frequently misunderstood. dma_cac

refactor dma_cache_sync V2

2017-10-03 Thread Christoph Hellwig
The dma_cache_sync routines is used to flush caches for memory returned by dma_alloc_attrs with the DMA_ATTR_NON_CONSISTENT flag (or previously from dma_alloc_noncoherent), but the requirements for it seems to be frequently misunderstood. dma_cache_sync is documented to be a no-op for allocations