nvme-loop: handle cpu unplug when re-establishing the controller

Browse source

If a cpu unplug event has occured, we need to take the minimum
of the provided nr_io_queues and the number of online cpus,
otherwise we won't be able to connect them as blk-mq mapping
won't dispatch to those queues.

Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>

...

This commit is contained in:

Sagi Grimberg 2017-03-13 13:27:51 +02:00 • committed by Jens Axboe

parent d476983ea0

commit 6ecda70ea9

1 changed files with 50 additions and 38 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

88

drivers/nvme/target/loop.c

View file