public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: device-mapper development <dm-devel@redhat.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Remove capping from dev_loss_tmo
Date: Wed, 16 Dec 2009 10:33:27 -0500	[thread overview]
Message-ID: <4B28FDC7.6020006@emulex.com> (raw)
In-Reply-To: <20091215082606.A45B037AD2@ochil.suse.de>

Hannes,

Not sure I quite agree with your description of the two timers - but 
relative to the goal of
allowing a larger dev_loss_tmo when fast_io_fail_tmo is enabled, it's 
fine.  Interestingly, I
was looking at when it's disabled, does the cap kick back in - and 
realized that once we
enable fast fail, we don't allow it to be turned off.

Looks good.

Acked-by:  James Smart  <james.smart@emulex.com>

-- james s

Hannes Reinecke wrote:
> Currently dev_loss_tmo is capped by SCSI_DEVICE_BLOCK_MAX_TIMEOUT.
> This causes problem with multipathing when the 'no_path_retry' setting
> exceeds the dev_loss_tmo setting, as then the system might run into
> a deadlock when all paths have been removed temporarily for longer
> than dev_loss_tmo.
> The principal reasons for the capping has been that we should
> not allow a remote port to remain in status 'blocked' indefinitely,
> so the capping is there to ensure that the port status is being reset
> eventually.
> However, the fast_io_fail_tmo will also move the remote port out of
> the 'blocked' state, so for any HBA driver implementing both the
> capping should really be on the fast_io_fail_tmo, and not on the
> dev_loss_tmo.
> This patch implements just that, ie the fast_io_fail_tmo is capped
> to SCSI_DEVICE_BLOCK_TIMEOUT and the capping is removed from
> dev_loss_tmo when fast_io_fail_tmo is set.
> This allows us to synchronize the dev_loss_tmo setting to the
> 'no_path_retry' setting from multipathing thus avoiding the deadlock.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
>
> diff --git a/drivers/scsi/scsi_transport_fc.c b/drivers/scsi/scsi_transport_fc.c
> index 573ce21..6f39bf4 100644
> --- a/drivers/scsi/scsi_transport_fc.c
> +++ b/drivers/scsi/scsi_transport_fc.c
> @@ -475,7 +475,8 @@ MODULE_PARM_DESC(dev_loss_tmo,
>  		 "Maximum number of seconds that the FC transport should"
>  		 " insulate the loss of a remote port. Once this value is"
>  		 " exceeded, the scsi target is removed. Value should be"
> -		 " between 1 and SCSI_DEVICE_BLOCK_MAX_TIMEOUT.");
> +		 " between 1 and SCSI_DEVICE_BLOCK_MAX_TIMEOUT if"
> +		 " fast_io_fail_tmo is not set.");
>  
>  /*
>   * Netlink Infrastructure
> @@ -831,9 +832,17 @@ store_fc_rport_dev_loss_tmo(struct device *dev, struct device_attribute *attr,
>  	    (rport->port_state == FC_PORTSTATE_NOTPRESENT))
>  		return -EBUSY;
>  	val = simple_strtoul(buf, &cp, 0);
> -	if ((*cp && (*cp != '\n')) ||
> -	    (val < 0) || (val > SCSI_DEVICE_BLOCK_MAX_TIMEOUT))
> +	if ((*cp && (*cp != '\n')) || (val < 0))
>  		return -EINVAL;
> +
> +	/*
> +	 * If fast_io_fail is off we have to cap
> +	 * dev_loss_tmo at SCSI_DEVICE_BLOCK_MAX_TIMEOUT
> +	 */
> +	if (rport->fast_io_fail_tmo == -1 &&
> +	    val > SCSI_DEVICE_BLOCK_MAX_TIMEOUT)
> +		return -EINVAL;
> +
>  	i->f->set_rport_dev_loss_tmo(rport, val);
>  	return count;
>  }
> @@ -914,9 +923,16 @@ store_fc_rport_fast_io_fail_tmo(struct device *dev,
>  		rport->fast_io_fail_tmo = -1;
>  	else {
>  		val = simple_strtoul(buf, &cp, 0);
> -		if ((*cp && (*cp != '\n')) ||
> -		    (val < 0) || (val >= rport->dev_loss_tmo))
> +		if ((*cp && (*cp != '\n')) || (val < 0))
>  			return -EINVAL;
> +		/*
> +		 * Cap fast_io_fail by dev_loss_tmo or
> +		 * SCSI_DEVICE_BLOCK_MAX_TIMEOUT.
> +		 */
> +		if ((val >= rport->dev_loss_tmo) ||
> +		    (val > SCSI_DEVICE_BLOCK_MAX_TIMEOUT))
> +			return -EINVAL;
> +
>  		rport->fast_io_fail_tmo = val;
>  	}
>  	return count;
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>
>   

  parent reply	other threads:[~2009-12-16 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15  8:26 [PATCH] Remove capping from dev_loss_tmo Hannes Reinecke
2009-12-15  8:54 ` Mike Christie
2009-12-15  9:53   ` Hannes Reinecke
2009-12-17  2:40     ` Mike Christie
2009-12-17  2:43       ` Mike Christie
2009-12-16 15:33 ` James Smart [this message]
2009-12-16 15:34 ` James Smart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B28FDC7.6020006@emulex.com \
    --to=james.smart@emulex.com \
    --cc=James.Bottomley@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox