From: Grant Grundler <grundler@dsl2.external.hp.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Richard Hirst <rhirst@linuxcare.com>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: tag starvation
Date: Sun, 27 Jan 2002 12:05:06 -0700 [thread overview]
Message-ID: <20020127190506.DD761482A@dsl2.external.hp.com> (raw)
In-Reply-To: Message from James Bottomley <James.Bottomley@HansenPartnership.com> of "Sun, 27 Jan 2002 11:52:53 EST." <200201271652.g0RGqrA02016@localhost.localdomain>
James Bottomley wrote:
> Actually, I looked and the timeout is now 10s, not 2s.
Ah ok. then really the question is if this happens with HP firmware or not.
(Eg ST15150WD should have HP12 firmware rev, iirc). I don't expect it to.
> The upper device
> drivers (st, sd etc.) do get to override this. The problems tend to come
> when the error recovery takes over.
errory recovery is a nightmare. For HPUX, we concluded we coudn't safely
guarantee the bus would be cleared until about 45 seconds after an IO
had be initiated. Roughly in the following order:
30 sec IO timeout
10 sec abort cmd to timeout (attempt to kill the original IO)
5 sec post-reset delay (SCSI device recovery from bus reset)
Shortening the 30 second timer could be done but it would require
more restrictions on how much IO is going across the bus. non-trivial
problem given these were SCSI clusters.
grant
next prev parent reply other threads:[~2002-01-27 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-26 17:23 [parisc-linux] Re: tag starvation James Bottomley
2002-01-27 8:41 ` Grant Grundler
2002-01-27 16:52 ` James Bottomley
2002-01-27 19:05 ` Grant Grundler [this message]
[not found] <200201240200.VAA00858@monmouth.com>
2002-01-25 6:55 ` Grant Grundler
2002-01-25 9:57 ` Richard Hirst
2002-01-26 5:28 ` Grant Grundler
2002-01-26 17:22 ` Richard Hirst
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=20020127190506.DD761482A@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rhirst@linuxcare.com \
/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