public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: michaelc@cs.wisc.edu
Cc: linux-scsi@vger.kernel.org, jens.axboe@oracle.com,
	Mike Christie <mchristi@redhat.com>
Subject: Re: [PATCH 1/1] block: set req->timeout in blk_add_timer
Date: Sat, 06 Sep 2008 08:10:20 -0500	[thread overview]
Message-ID: <1220706621.3430.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1220680240-27724-1-git-send-email-michaelc@cs.wisc.edu>

On Sat, 2008-09-06 at 00:50 -0500, michaelc@cs.wisc.edu wrote:
> From: Mike Christie <mchristi@redhat.com>
> 
> To prevent a reques from running forever, scsi-ml checks if
> a command has been running req->timeout * cmd->allowed + 1 seconds.
> If it has, scsi-ml will fail the request. From what I can tell
> it looks like in Jen's tree that the block layer is not setting
> this value, so a command is failed right away a lot of times because
> wait_for in scsi_softirq_done is zero seconds. It is only set by ioctls
> and passthrough.
> 
> This patch just copies the q timeout that is used, so any one
> checking it will still be able to see it.
> 
> For the scsi-ml req->timeout usage, I think we can move the retries and
> the infinite retry check from the scsi layer to the block layer. I was
> not sure if we should do that in this patch or a separate one. I can
> cook up another patch if people want. If it would be possible to do
> that after MikeA's patches it would probably be best though since
> he is working on that code too.

Sure, basically move all responsibility for retries to block.  That will
require a few other things like abstracting scsi_decide_disposition.  I
actually had an impression from one of the storage summits that someone
was working on this.

James



  reply	other threads:[~2008-09-06 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06  5:50 [PATCH 1/1] block: set req->timeout in blk_add_timer michaelc
2008-09-06 13:10 ` James Bottomley [this message]
2008-09-06 13:34   ` Mike Christie
2008-09-08  7:38 ` Jens Axboe

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=1220706621.3430.1.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jens.axboe@oracle.com \
    --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