diff options
| author | Omar Sandoval <osandov@fb.com> | 2017-04-07 08:53:11 -0600 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2017-04-07 08:56:49 -0600 |
| commit | ebe8bddb6e30d7a02775b9972099271fc5910f37 (patch) | |
| tree | bf15660fb38869b2e4edc574a20b4415c9cd5cf6 /block/Kconfig | |
| parent | 54d5329d425650fafaf90660a139c771d2d49cae (diff) | |
| download | linux-ebe8bddb6e30d7a02775b9972099271fc5910f37.tar.gz linux-ebe8bddb6e30d7a02775b9972099271fc5910f37.tar.bz2 linux-ebe8bddb6e30d7a02775b9972099271fc5910f37.zip | |
blk-mq: remap queues when adding/removing hardware queues
blk_mq_update_nr_hw_queues() used to remap hardware queues, which is the
behavior that drivers expect. However, commit 4e68a011428a changed
blk_mq_queue_reinit() to not remap queues for the case of CPU
hotplugging, inadvertently making blk_mq_update_nr_hw_queues() not remap
queues as well. This breaks, for example, NBD's multi-connection mode,
leaving the added hardware queues unused. Fix it by making
blk_mq_update_nr_hw_queues() explicitly remap the queues.
Fixes: 4e68a011428a ("blk-mq: don't redistribute hardware queues on a CPU hotplug event")
Reviewed-by: Keith Busch <keith.busch@intel.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'block/Kconfig')
0 files changed, 0 insertions, 0 deletions