[PATCH for-4.12-rc] nvme-rdma: fast fail incoming requests while we reconnect
Sagi Grimberg
sagi at grimberg.me
Tue Jun 6 11:28:24 PDT 2017
>>> +static inline int nvme_rdma_queue_is_ready(struct nvme_rdma_queue *queue,
>>> struct request *rq)
>>> {
>>> if (unlikely(!test_bit(NVME_RDMA_Q_LIVE, &queue->flags))) {
>>> @@ -1441,11 +1443,22 @@ static inline bool nvme_rdma_queue_is_ready(struct nvme_rdma_queue *queue,
>>>
>>> if (!blk_rq_is_passthrough(rq) ||
>>> cmd->common.opcode != nvme_fabrics_command ||
>>> - cmd->fabrics.fctype != nvme_fabrics_type_connect)
>>> - return false;
>>> + cmd->fabrics.fctype != nvme_fabrics_type_connect) {
>>> + /*
>>> + * reconnecting state means transport disruption, which
>>> + * can take a long time and even might fail permanently,
>>> + * so we can't let incoming I/O be requeued forever.
>>> + * fail it fast to allow upper layers a chance to
>>> + * failover.
>>> + */
>>> + if (queue->ctrl->ctrl->state == NVME_CTRL_RECONNECTING)
>>
>> Sagi/Christoph,
>> It should be queue->ctrl->ctrl.state.
>>
>> we are testing this patch also now.
>
> I've fixed this up already. Especially as the earlier version got it
> right :)
Baa how did that sneak in....
Sorry, thanks Max & Christoph!
More information about the Linux-nvme
mailing list