diff options
author | Chao Gao <chao.gao@intel.com> | 2022-04-13 08:32:22 +0200 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2022-04-14 06:30:39 +0200 |
commit | 9e02977bfad006af328add9434c8bffa40e053bb (patch) | |
tree | fdd9d545aa8ae964f424f2be43bcd3cd61be2b7f /kernel/kprobes.c | |
parent | dma-mapping: move pgprot_decrypted out of dma_pgprot (diff) | |
download | linux-9e02977bfad006af328add9434c8bffa40e053bb.tar.xz linux-9e02977bfad006af328add9434c8bffa40e053bb.zip |
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: 55897af63091 ("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>
Diffstat (limited to 'kernel/kprobes.c')
0 files changed, 0 insertions, 0 deletions