From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Linas Vepstas <linas@austin.ibm.com>,
linux-scsi@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: PCI Error Recovery: Symbios SCSI device driver
Date: Tue, 31 Oct 2006 14:24:01 -0500 [thread overview]
Message-ID: <1162322643.13859.54.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20061031185506.GE26964@parisc-linux.org>
On Tue, 2006-10-31 at 11:55 -0700, Matthew Wilcox wrote:
> Is it safe / reasonable / a good idea to sleep for 35 seconds in the EH
> handler? I'm not that familiar with how the EH code works. It has its
> own thread, so I suppose that's OK.
Yes, each host has its own thread. Ordinarily it would be impolite to
delay recovery this long, but I assume that since the card is wedged
there's nothing else it could be doing anyway.
Just for my own edification, what happens on the dual function (dual
channel) boards? We have two threads there and two separate I/O
processors. I assume a PCI error will kill both, do we need to do
something about this?
James
> I generally prefer not to be so perlish in conditionals, ie:
>
> if ((np->s.device->error_state != pci_channel_io_normal) &&
> (np->s.device->error_state != 0) {
> int timed_out = wait_for_completion_timeout(
> &np->s.io_reset_wait, WAIT_FOR_PCI_RECOVERY*HZ);
> if (!timed_out)
> return SCSI_FAILED;
> }
>
> Why is the condition so complicated though? What does 0 mean if it's
> not io_normal? At least let's hide that behind a convenience macro:
>
next prev parent reply other threads:[~2006-10-31 19:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:05 Linas Vepstas
2006-10-31 18:55 ` Matthew Wilcox
2006-10-31 19:24 ` James Bottomley [this message]
2006-10-31 22:26 ` Linas Vepstas
2006-10-31 23:13 ` Linas Vepstas
2006-11-02 0:07 ` [PATCH v3]: " Linas Vepstas
2006-11-02 1:19 ` [PATCH v4]: " Linas Vepstas
2006-11-02 3:57 ` Matthew Wilcox
2006-11-02 4:46 ` [PATCH]: " Grant Grundler
2006-11-02 4:56 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2007-07-02 18:39 Linas Vepstas
2007-07-05 18:28 ` Andrew Morton
2007-07-05 18:54 ` Matthew Wilcox
2007-08-02 22:53 ` Linas Vepstas
2006-09-21 23:13 Linas Vepstas
2006-09-22 22:06 ` Luca
2006-09-22 23:32 ` Linas Vepstas
2006-09-22 23:39 ` Randy.Dunlap
2006-09-22 23:50 ` Linas Vepstas
2006-09-23 0:57 ` Randy.Dunlap
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=1162322643.13859.54.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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
Powered by JetHome