diff options
| author | Sagi Grimberg <sagi@grimberg.me> | 2016-09-02 09:01:54 -0700 |
|---|---|---|
| committer | Sagi Grimberg <sagi@grimberg.me> | 2016-09-12 22:29:34 +0300 |
| commit | e89ca58f9c901c8c4cfb09f96d879b186bb01492 (patch) | |
| tree | ade1f8ddcb820d9a9afc5fe63a2050ff45fadfa9 /Documentation | |
| parent | f361e5a01ed35c0f9a00816d76a910d8a5cb4547 (diff) | |
nvme-rdma: add DELETING queue flag
When we get a surprise disconnect from the target we queue a periodic
reconnect (which is the sane thing to do...).
We only move the queues out of CONNECTED when we retry to reconnect (after
10 seconds in the default case) but we stop the blk queues immediately
so we are not bothered with traffic from now on. If delete() is kicking
off in this period the queues are still in CONNECTED state.
Part of the delete sequence is trying to issue ctrl shutdown if the
admin queue is CONNECTED (which it is!). This request is issued but
stuck in blk-mq waiting for the queues to start again. This might be
the one preventing us from forward progress...
The patch separates the queue flags to CONNECTED and DELETING. Now we
will move out of CONNECTED as soon as error recovery kicks in (before
stopping the queues) and DELETING is on when we start the queue deletion.
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions