public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Min Zhang <mzhang@mvista.com>
Cc: Tejun Heo <tj@kernel.org>,
	James Bottomley <James.Bottomley@suse.de>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: timeout reset timer before command is queued
Date: Tue, 15 Dec 2009 15:16:32 +0200	[thread overview]
Message-ID: <4B278C30.9020209@panasas.com> (raw)
In-Reply-To: <4B26E38C.1000605@mvista.com>

On 12/15/2009 03:17 AM, Min Zhang wrote:
<snip>

> 
> Boaz, i think your patch will make scsi_request_fn always goto not_ready 
> and skip scsi_dispatch_cmd, because after removing blk_queue_start_tag, 
> subsequent if (blk_queue_tagged(q) && !blk_rq_tagged(req)) is always 
> true. The original blk_queue_start_tag is necessary to set REQ_QUEUE so 
> that blk_rq_tagged check can pass for dispatching. I don't see the other 
> blk_queue_start_tag call.
> 

You're absolutely right. I got mixed up between blk_queue_start_tag && blk_rq_tagged
So I missed the call to blk_queue_start_tag.

> Also timeout failure can still occur after scsi_request_fn unlock the 
> host_lock and before scsi_dispatch_cmd re-lock it.
> 

This was exactly my intention, to do all the things that can fail and the unlocking
then relocking before we start the request. And leave no failing possibility and lock
released between the start of the request and the dispatching. I think it would be wroth it.

But it's your call

Boaz

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11  2:41 [PATCH] scsi: timeout reset timer before command is queued Min Zhang
2009-12-13  9:52 ` Boaz Harrosh
2009-12-15  1:17   ` Min Zhang
2009-12-15  2:21     ` Matthew Wilcox
2009-12-15  2:40       ` Min Zhang
2009-12-15  2:59         ` Matthew Wilcox
2009-12-15 10:40         ` Matthew Wilcox
2009-12-15 13:16     ` Boaz Harrosh [this message]
2009-12-15 20:53       ` Min Zhang

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=4B278C30.9020209@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mzhang@mvista.com \
    --cc=tj@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