From 6a92967ccbfc20f94055c9a94bf951230cbd0452 Mon Sep 17 00:00:00 2001 From: Sagi Grimberg Date: Wed, 22 Jun 2016 15:06:01 +0300 Subject: nvme-fabrics: Remove tl_retry_count The timeout before error recovery logic kicks in is dictated by the nvme keep-alive, so we don't really need a transport layer retry count. transports can retry for as much as they like. Signed-off-by: Sagi Grimberg Signed-off-by: Jens Axboe --- drivers/nvme/host/fabrics.h | 3 --- 1 file changed, 3 deletions(-) (limited to 'drivers/nvme/host/fabrics.h') diff --git a/drivers/nvme/host/fabrics.h b/drivers/nvme/host/fabrics.h index b54067404963..89df52c8be97 100644 --- a/drivers/nvme/host/fabrics.h +++ b/drivers/nvme/host/fabrics.h @@ -69,8 +69,6 @@ enum { * @trsvcid: network port used for host-controller communication. * @queue_size: Number of IO queue elements. * @nr_io_queues: Number of controller IO queues that will be established. - * @tl_retry_count: Number of transport layer retries for a fabric queue before - * kicking upper layer(s) error recovery. * @reconnect_delay: Time between two consecutive reconnect attempts. * @discovery_nqn: indicates if the subsysnqn is the well-known discovery NQN. * @kato: Keep-alive timeout. @@ -84,7 +82,6 @@ struct nvmf_ctrl_options { char *trsvcid; size_t queue_size; unsigned int nr_io_queues; - unsigned short tl_retry_count; unsigned int reconnect_delay; bool discovery_nqn; unsigned int kato; -- cgit