projects
/
GitHub
/
moto-9609
/
android_kernel_motorola_exynos9610.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
4c8b99f
)
nvme-loop: update tagset nr_hw_queues after reconnecting/resetting
author
Sagi Grimberg
<sagi@grimberg.me>
Thu, 29 Jun 2017 08:13:43 +0000
(11:13 +0300)
committer
Sagi Grimberg
<sagi@grimberg.me>
Tue, 4 Jul 2017 06:44:16 +0000
(09:44 +0300)
We might have more/less queues once we reconnect/reset. For
example due to cpu going online/offline
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
drivers/nvme/target/loop.c
patch
|
blob
|
blame
|
history
diff --git
a/drivers/nvme/target/loop.c
b/drivers/nvme/target/loop.c
index 568ed86256968f83fd300f357b300983a88eac6b..3d51341e62ee5316ac1845914e3e3712b3b25ac3 100644
(file)
--- a/
drivers/nvme/target/loop.c
+++ b/
drivers/nvme/target/loop.c
@@
-508,6
+508,9
@@
static void nvme_loop_reset_ctrl_work(struct work_struct *work)
if (ret)
goto out_destroy_io;
+ blk_mq_update_nr_hw_queues(&ctrl->tag_set,
+ ctrl->ctrl.queue_count - 1);
+
changed = nvme_change_ctrl_state(&ctrl->ctrl, NVME_CTRL_LIVE);
WARN_ON_ONCE(!changed);