]> git.baikalelectronics.ru Git - kernel.git/commit
dma-direct: avoid redundant memory sync for swiotlb
authorChao Gao <chao.gao@intel.com>
Wed, 13 Apr 2022 06:32:22 +0000 (08:32 +0200)
committerChristoph Hellwig <hch@lst.de>
Thu, 14 Apr 2022 04:30:39 +0000 (06:30 +0200)
commit89e68e5385833fc1fe86245fedfea0f666237b54
treefdd9d545aa8ae964f424f2be43bcd3cd61be2b7f
parentd715fb24e167c3271287c5e309995f7e0fd19bc8
dma-direct: avoid redundant memory sync for swiotlb

When we looked into FIO performance with swiotlb enabled in VM, we found
swiotlb_bounce() is always called one more time than expected for each DMA
read request.

It turns out that the bounce buffer is copied to original DMA buffer twice
after the completion of a DMA request (one is done by in
dma_direct_sync_single_for_cpu(), the other by swiotlb_tbl_unmap_single()).
But the content in bounce buffer actually doesn't change between the two
rounds of copy. So, one round of copy is redundant.

Pass DMA_ATTR_SKIP_CPU_SYNC flag to swiotlb_tbl_unmap_single() to
skip the memory copy in it.

This fix increases FIO 64KB sequential read throughput in a guest with
swiotlb=force by 5.6%.

Fixes: 601f7fb0b0b1 ("dma-direct: merge swiotlb_dma_ops into the dma_direct code")
Reported-by: Wang Zhaoyang1 <zhaoyang1.wang@intel.com>
Reported-by: Gao Liang <liang.gao@intel.com>
Signed-off-by: Chao Gao <chao.gao@intel.com>
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
kernel/dma/direct.h