public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Mike Anderson <andmike@us.ibm.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Requested changes for the SCSI error handler
Date: 08 Jun 2004 11:26:30 -0500	[thread overview]
Message-ID: <1086711994.2105.18.camel@mulgrave> (raw)
In-Reply-To: <20040604232344.GA3214@us.ibm.com>

On Fri, 2004-06-04 at 18:23, Mike Anderson wrote:
> Looks ok. I know your patch is in line with James requests, but I had a
> counter idea that allows for setting the settle delays up, down, or to
> zero post scsi_host_alloc. If the LLDD does nothing behavior should not
> change. This would allow increasing settle if some LLDD wanted it and
> also set it through sysfs if we wanted that in the future.  You can
> throw this patch in the bit bucket if you want to go the previously
> stated direction.

Well, how about a compromise?  I like the ability to alter the host
settle time; however, I think turning these over to the driver to sort
out how it pleases gives the LLD more control in this situation,
certainly for the HOST reset.

I'm less sure that a bus reset timeout belongs in the LLD, but I suppose
that could be pulled into the SPI transport class eventually.

So, what about Alan's approach using a single flag to give the LLD
control, but give it control for both the host and bus resets?

James



  parent reply	other threads:[~2004-06-08 16:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 18:50 Requested changes for the SCSI error handler Alan Stern
2004-06-01 19:58 ` James Bottomley
2004-06-01 20:29   ` Alan Stern
2004-06-01 20:46     ` James Bottomley
2004-06-04 20:59       ` Alan Stern
2004-06-04 23:23         ` Mike Anderson
2004-06-05 22:41           ` Alan Stern
2004-06-08 16:26           ` James Bottomley [this message]
2004-06-08 17:19             ` Mike Anderson
2004-06-08 18:31             ` Alan Stern
2004-06-08 18:39               ` Mike Anderson
2004-06-08 22:00               ` James Bottomley

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=1086711994.2105.18.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=andmike@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.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