RFC blk-mq/nvme: use blk_mq_alloc_request() for NVMe's connect request
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | block: reuse one scheduler/flush field for private request's datainclude/ | +5 | 0 replies | |
| 2/3 | nvme: don't use blk_mq_alloc_request_hctx() for allocating connect requestdrivers/ drivers/ drivers/ +2 more | +127 | 0 replies | |
| 3/3 | blk-mq: kill blk_mq_alloc_request_hctx()block/ include/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/3] blk-mq/nvme: use blk_mq_alloc_request() for NVMe's connect request
Hi,
Use blk_mq_alloc_request() for allocating NVMe loop, fc, rdma and tcp's connect request, and selecting transport queue runtime for connect request.
Then kill blk_mq_alloc_request_hctx().
Ming Lei (3):
block: reuse one scheduler/flush field for private request's data
nvme: don't use blk_mq_alloc_request_hctx() for allocating connect
request
blk-mq: kill blk_mq_alloc_request_hctx()
block/blk-mq.c | 46 -------------------------------------- drivers/nvme/host/core.c | 9 +++----- drivers/nvme/host/fc.c | 10 +++++++++ drivers/nvme/host/rdma.c | 40 ++++++++++++++++++++++++++++++--- drivers/nvme/host/tcp.c | 41 ++++++++++++++++++++++++++++++--- drivers/nvme/target/loop.c | 42 +++++++++++++++++++++++++++++++--- include/linux/blk-mq.h | 3 --- include/linux/blkdev.h | 6 ++++- 8 files changed, 132 insertions(+), 65 deletions(-)
Cc James Smart <[email protected]>
Cc Sagi Grimberg <[email protected]>
Signature · 1 line
2.20.1