linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: michaelc@cs.wisc.edu
Cc: linux-scsi@vger.kernel.org, Mike Christie <mchristi@redhat.com>,
	"James.Bottomley@suse.de" <James.Bottomley@suse.de>
Subject: Re: [PATCH 1/1] scsi/block: increase flush/sync timeout v2
Date: Mon, 23 Aug 2010 12:35:53 +0200	[thread overview]
Message-ID: <4C724F09.8030209@kernel.dk> (raw)
In-Reply-To: <1281542785-31395-1-git-send-email-michaelc@cs.wisc.edu>

On 2010-08-11 18:06, michaelc@cs.wisc.edu wrote:
> From: Mike Christie <mchristi@redhat.com>
> 
> We have been seeing the flush request timeout with a wide
> range of hardware from tgt+iser to FC targets from a major vendor.
> 
> After discussions about if the value should be configurable and
> what the best value should be, this patch just increases the flush/sync
> cache timeout to 1 minute. 2 minutes was determined to be too long, and
> making it configurable was troublesome for users.
> 
> This patch was made over Linus's tree. It is not made over scsi-misc
> or scsi-rc-fixes, because Linus's had block layer changes that my
> patch was built over.
> 

Looks fine to me. James? Leaving patch below.

Acked-by: Jens Axboe <jaxboe@fusionio.com>


>  drivers/scsi/sd.c |    4 ++--
>  drivers/scsi/sd.h |    1 +
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 8e2e893..f7e79e3 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -477,7 +477,7 @@ static int scsi_setup_discard_cmnd(struct scsi_device *sdp, struct request *rq)
>  
>  static int scsi_setup_flush_cmnd(struct scsi_device *sdp, struct request *rq)
>  {
> -	rq->timeout = SD_TIMEOUT;
> +	rq->timeout = SD_FLUSH_TIMEOUT;
>  	rq->retries = SD_MAX_RETRIES;
>  	rq->cmd[0] = SYNCHRONIZE_CACHE;
>  	rq->cmd_len = 10;
> @@ -1072,7 +1072,7 @@ static int sd_sync_cache(struct scsi_disk *sdkp)
>  		 * flush everything.
>  		 */
>  		res = scsi_execute_req(sdp, cmd, DMA_NONE, NULL, 0, &sshdr,
> -				       SD_TIMEOUT, SD_MAX_RETRIES, NULL);
> +				       SD_FLUSH_TIMEOUT, SD_MAX_RETRIES, NULL);
>  		if (res == 0)
>  			break;
>  	}
> diff --git a/drivers/scsi/sd.h b/drivers/scsi/sd.h
> index f81a930..315ce9d 100644
> --- a/drivers/scsi/sd.h
> +++ b/drivers/scsi/sd.h
> @@ -19,6 +19,7 @@
>   */
>  #define SD_TIMEOUT		(30 * HZ)
>  #define SD_MOD_TIMEOUT		(75 * HZ)
> +#define SD_FLUSH_TIMEOUT	(60 * HZ)
>  
>  /*
>   * Number of allowed retries


-- 
Jens Axboe


      reply	other threads:[~2010-08-23 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 16:06 [PATCH 1/1] scsi/block: increase flush/sync timeout v2 michaelc
2010-08-23 10:35 ` Jens Axboe [this message]

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=4C724F09.8030209@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=James.Bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mchristi@redhat.com \
    --cc=michaelc@cs.wisc.edu \
    /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;
as well as URLs for NNTP newsgroup(s).