Skip to content

passthru block optimizations

Jens Axboe linux-block 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3block: shrink rq_map_data a bitblock/blk-map.c include/linux/blk-mq.h+5 -51 reply
2/3block: enable bio caching use for passthru IOblock/blk-map.c+25 -83 replies
3/3block: use on-stack page vec for <= UIO_FASTIOVblock/blk-map.c+11 -31 reply

Reviews trailers per patch

All 3 patches have a Reviewed-by or Acked-by.

PatchChaitanya Kulkarni
1/3R-b
2/3R-b
3/3R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCHSET 0/3] passthru block optimizations

Hi,

Currently passthru IO is slower than bdev O_DIRECT. One of the reasons is that we do two allocations for each IO:

- One alloc+free for the page array for mapping the data
- One alloc+free of the bio

Let passthru IO dip into the bio cache to eliminate that one, and use UIO_FASTIOV to gate whether we need to alloc+free the page array for mapping purposes.

This closes about half of the gap between passthru and bdev dio for me. If we can sanely wire up completion batching for passthru, then that would almost fully close the gap. Outside of that, the main missing feature for passthru is the ability to use registered buffers with io_uring, as the per-io get_user_pages() is a large cycle consumer as well.

Signature · 1 line
Jens Axboe