public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: "michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/1] fc class: fail fast bsg requests
Date: Thu, 5 Nov 2009 13:39:54 -0500	[thread overview]
Message-ID: <4AF31BFA.1030305@emulex.com> (raw)
In-Reply-To: <1257441489-9055-1-git-send-email-michaelc@cs.wisc.edu>

Does this really do what you want ?  Don't you want something that dequeues 
the request, and errors it out ?

The break from the look doesn't remove the request from the request queue. It 
just stops servicing it.  Thus, we have the "goose" function that kicks in if 
the rport comes back, and if it doesn't, the queue gets removed (hmmm... now 
that I think about it - I'm not sure what happens if the request queue has 
items on it and the device gets torn down. Are we doing the right thing by 
references, etc?).

So - to have what you want, I would think we need to add:
- something that gooses the queue when fastfail io timeout expires
- allows the requests to enter between fastfail io timeout and nodev
   timeout and fails them.

It also says we aren't discriminating based on request type - e.g. any bsg 
request fails back immediately after fastfail io timer. Nothing ever waits 
until nodev tmo unless fastfail isn't configured.

Right ?

-- james s


michaelc@cs.wisc.edu wrote:
> From: Mike Christie <michaelc@cs.wisc.edu>
> 
> If the port state is blocked and the fast io fail tmo has
> fired then this patch will fail bsg requests immediately.
> This is needed if userspace is sending IOs to test the transport
> like with fcping, so it will not have to wait for the dev loss tmo.
> With this patch he bsg req fast io fail code behaves like the normal
> and sg io/passthrough fast io fail.
> 
> Patch was made over scsi-rc-fixes. It is only compiled tested.
> I found this while looking over the iscsi bsg patch.
> 
> Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
> Cc: james.smart@emulex.com <james.smart@emulex.com>
> ---
>  drivers/scsi/scsi_transport_fc.c |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/scsi/scsi_transport_fc.c b/drivers/scsi/scsi_transport_fc.c
> index c6f70da..1004684 100644
> --- a/drivers/scsi/scsi_transport_fc.c
> +++ b/drivers/scsi/scsi_transport_fc.c
> @@ -3769,8 +3769,9 @@ fc_bsg_request_handler(struct request_queue *q, struct Scsi_Host *shost,
>  		return;
>  
>  	while (!blk_queue_plugged(q)) {
> -		if (rport && (rport->port_state == FC_PORTSTATE_BLOCKED))
> -				break;
> +		if (rport && (rport->port_state == FC_PORTSTATE_BLOCKED) &&
> +		    !(rport->flags & FC_RPORT_FAST_FAIL_TIMEDOUT))
> +			break;
>  
>  		req = blk_fetch_request(q);
>  		if (!req)

  reply	other threads:[~2009-11-05 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05 17:18 [PATCH 1/1] fc class: fail fast bsg requests michaelc
2009-11-05 18:39 ` James Smart [this message]
2009-11-05 18:55   ` Mike Christie
2009-11-05 19:02     ` 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=4AF31BFA.1030305@emulex.com \
    --to=james.smart@emulex.com \
    --cc=linux-scsi@vger.kernel.org \
    --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