summaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorSagi Grimberg <sagi@grimberg.me>2016-06-13 16:45:28 +0200
committerJens Axboe <axboe@fb.com>2016-07-05 11:28:20 -0600
commit038bd4cb6766c69b5b9c77507f389cc718a36842 (patch)
treef551977e651401dadf30bb47bc9756df5f922901 /block
parent7b89eae29eec4dd9259acd82ed57bec8d9e430ca (diff)
downloadlinux-038bd4cb6766c69b5b9c77507f389cc718a36842.tar.gz
linux-038bd4cb6766c69b5b9c77507f389cc718a36842.tar.bz2
linux-038bd4cb6766c69b5b9c77507f389cc718a36842.zip
nvme: add keep-alive support
Periodic keep-alive is a mandatory feature in NVMe over Fabrics, and optional in NVMe 1.2.1 for PCIe. This patch adds periodic keep-alive sent from the host to verify that the controller is still responsive and vice-versa. The keep-alive timeout is user-defined (with keep_alive_tmo connection parameter) and defaults to 5 seconds. In order to avoid a race condition where the host sends a keep-alive competing with the target side keep-alive timeout expiration, the host adds a grace period of 10 seconds when publishing the keep-alive timeout to the target. In case a keep-alive failed (or timed out), a transport specific error recovery kicks in. For now only NVMe over Fabrics is wired up to support keep alive, but we can add PCIe support easily once controllers actually supporting it become available. Signed-off-by: Sagi Grimberg <sagi@grimberg.me> Reviewed-by: Steve Wise <swise@chelsio.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Keith Busch <keith.busch@intel.com> Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions