diff options
author | Keith Busch <keith.busch@intel.com> | 2017-03-01 14:22:12 -0500 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2017-03-02 08:56:59 -0700 |
commit | 302ad8cc09339ea261eef58a8d5f4a116a8ffda5 (patch) | |
tree | 622b89d58a88a0f3f241933386522224394e6f49 /drivers/vlynq | |
parent | f91328c40a559362b6e7b7bfee01ca17fda87592 (diff) | |
download | blackbird-op-linux-302ad8cc09339ea261eef58a8d5f4a116a8ffda5.tar.gz blackbird-op-linux-302ad8cc09339ea261eef58a8d5f4a116a8ffda5.zip |
nvme: Complete all stuck requests
If the nvme driver is shutting down its controller, the drievr will not
start the queues up again, preventing blk-mq's hot CPU notifier from
making forward progress.
To fix that, this patch starts a request_queue freeze when the driver
resets a controller so no new requests may enter. The driver will wait
for frozen after IO queues are restarted to ensure the queue reference
can be reinitialized when nvme requests to unfreeze the queues.
If the driver is doing a safe shutdown, the driver will wait for the
controller to successfully complete all inflight requests so that we
don't unnecessarily fail them. Once the controller has been disabled,
the queues will be restarted to force remaining entered requests to end
in failure so that blk-mq's hot cpu notifier may progress.
Signed-off-by: Keith Busch <keith.busch@intel.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'drivers/vlynq')
0 files changed, 0 insertions, 0 deletions