check the number of hw queues mapped to sw queues
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 8 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | blk-mq: add a function to return number of hw queues mappedblock/ include/ | +16 | 0 replies | |
| 2/2 | nvme-rdma: check the number of hw queues mappeddrivers/ | +11 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] check the number of hw queues mapped to sw queues
From: Ming Lin <[email protected]>
Please see patch 2 for detail bug description.
Say, on a machine with 8 CPUs, we create 6 io queues(blk-mq hw queues)
echo "transport=rdma,traddr=192.168.2.2,nqn=testiqn,nr_io_queues=6" \
> /dev/nvme-fabrics
Then actually only 4 hw queues were mapped to CPU sw queues.
HW Queue 1 <-> CPU 0,4
HW Queue 2 <-> CPU 1,5
HW Queue 3 <-> None
HW Queue 4 <-> CPU 2,6
HW Queue 5 <-> CPU 3,7
HW Queue 6 <-> None
Back to Jan 2016, I send a patch:
[PATCH] blk-mq: check if all HW queues are mapped to cpu
http://www.spinics.net/lists/linux-block/msg01038.html
It adds check code to blk_mq_update_queue_map().
But it seems too aggresive because it's not an error that some hw queues were not mapped to sw queues.
So this series just add a new function blk_mq_hctx_mapped() to check how many hw queues were mapped. And the driver(for example, nvme-rdma) that cares about it will do the check.
Ming Lin (2):
blk-mq: add a function to return number of hw queues mapped
nvme-rdma: check the number of hw queues mapped
block/blk-mq.c | 15 +++++++++++++++ drivers/nvme/host/rdma.c | 11 +++++++++++ include/linux/blk-mq.h | 1 + 3 files changed, 27 insertions(+)
Signature · 1 line
1.9.1