linux

iv/linux

History

James Smart f673714a12 nvme-fc: shorten reconnect delay if possible for FC

We've had several complaints about a 10s reconnect delay (the default)
when there was an error while there is connectivity to a subsystem.
The max_reconnects and reconnect_delay are set in common code prior to
calling the transport to create the controller.

This change checks if the default reconnect delay is being used, and if
so, it adjusts it to a shorter period (2s) for the nvme-fc transport.
It does so by calculating the controller loss tmo window, changing the
value of the reconnect delay, and then recalculating the maximum number
of reconnect attempts allowed.

Signed-off-by: James Smart <james.smart@broadcom.com>
Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>

2020-10-23 12:54:45 +02:00

core.c

nvme: translate zone resource errors

2020-10-13 15:05:05 -06:00

fabrics.c

nvme-fabrics: allow to queue requests for live queues

2020-09-09 08:00:50 +02:00

fabrics.h

nvme: fix deadlock in disconnect during scan_work and/or ana_work

2020-07-29 07:45:19 +02:00

fault_inject.c

nvme: enable to inject errors into admin commands