Christoph Hellwig fafadcd165 swiotlb: don't dip into swiotlb pool for coherent allocations ...

All architectures that support swiotlb also have a zone that backs up
these less than full addressing allocations (usually ZONE_DMA32).

Because of that it is rather pointless to fall back to the global swiotlb
buffer if the normal dma direct allocation failed - the only thing this
will do is to eat up bounce buffers that would be more useful to serve
streaming mappings.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

2018-10-19 08:48:28 +02:00

..

coherent.c

…

contiguous.c

dma-mapping: fix panic caused by passing empty cma command line argument

2018-09-20 09:01:08 +02:00

debug.c

dma-debug: Check for drivers mapping invalid addresses in dma_map_single()

2018-10-08 09:44:17 +02:00

direct.c

swiotlb: remove the overflow buffer

2018-10-19 08:43:46 +02:00

Kconfig

dma-mapping: consolidate the dma mmap implementations

2018-09-20 09:01:16 +02:00

Makefile

dma-mapping: merge direct and noncoherent ops

2018-09-20 09:01:15 +02:00

mapping.c

dma-mapping: support non-coherent devices in dma_common_get_sgtable

2018-09-20 09:01:17 +02:00

swiotlb.c

swiotlb: don't dip into swiotlb pool for coherent allocations

2018-10-19 08:48:28 +02:00

virt.c

…