public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Brian King <brking@us.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: host_self_blocked question/bug?
Date: 25 Nov 2003 15:55:19 -0600	[thread overview]
Message-ID: <1069797320.1787.220.camel@mulgrave> (raw)
In-Reply-To: <3FC3CDCF.4030105@us.ibm.com>

On Tue, 2003-11-25 at 15:46, Brian King wrote:
> I am writing an HBA driver for 2.6 and found that when host_self_blocked 
> is true the error handler will still send Test Unit Ready. This seems 
> like a bug. I would like to be able to use scsi_block_requests to stop 
> anything from coming into queuecommand, as I may be running BIST on the 
> adapter, downloading microcode, etc. in which case I cannot accept any 
> commands. It seems to me like the solution might be to simply have 
> scsi_eh_tur return success in if host_self_blocked is true. Thoughts?

Not in isolation...what are you trying to do?

The original design was to allow short hiatuses when the HBA couldn't
accept I/O.  It doesn't work if there's I/O pending (unless the stop is
very short), because the SCSI timers are still ticking and error
recovery doesn't see this flag.

There has been talk of making this interface robust to pending commands
(halt the timers and freeze the error handler) for FC HBA's that take
ages to process loop events, but no work has been done on this---it's
quite a bit more work than simply not allowing the eh to emit TURs.

James



  reply	other threads:[~2003-11-25 21:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25 21:46 host_self_blocked question/bug? Brian King
2003-11-25 21:55 ` James Bottomley [this message]
2003-11-25 22:31   ` Brian King
2003-11-26  0:32     ` Patrick Mansfield
2003-11-26 13:44       ` Christoph Hellwig

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=1069797320.1787.220.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=brking@us.ibm.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