From: Brian King <brking@linux.vnet.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>,
linux-scsi@vger.kernel.org, thlin@linux.vnet.ibm.com,
linux-ide@vger.kernel.org, miltonm@bga.com
Subject: Re: [PATCH 1/1] ipr: Fix HDIO_GET_IDENTITY oops for SATA devices
Date: Mon, 02 Jun 2008 15:27:10 -0500 [thread overview]
Message-ID: <4844579E.80005@linux.vnet.ibm.com> (raw)
In-Reply-To: <1212435552.3369.62.camel@localhost.localdomain>
James Bottomley wrote:
> On Mon, 2008-06-02 at 14:54 -0400, Jeff Garzik wrote:
>> Brian King wrote:
>>> One thing that having a per-port SCSI host buys us is that it isolates
>>> EH to the port rather than the entire SCSI host. The way that the new
>>> libata EH is designed, it can end up spending a fair amount of time
>>> in EH and may even sleep for seconds at a time, waiting for the device
>>> to come ready. Quiescing all devices on a SAS host due to a single
>>> SATA device gets *very* painful. The new libata EH does much more than
>>> just EH. It wakes up for every ATAPI check condition...
>>>
>>> Before we can move to a single SCSI host model, we will
>>> have to make some changes regarding how EH is done in libata...
>>
>> Good points. There definitely needs to be a discussion about how to
>> integrate libata EH with libsas model and ipr model (which are distinct,
>> if similar).
>
> Actually, libsas completely hijacks the strategy handler (as I believe
> libata does), so it really no longer has a host dependency, except for
> the one thread per host thing. Most of what it does (unless it thinks
> the actual host chip is wedged) is port (as in SAS port, not phy) based,
> so I think we have the capability for doing this already.
libsas currently does hijack the strategy handler today, but if we want
to move it to the new libata EH/attach model, that's not going to work.
libata EH does much more than EH. Its really more of an exception handler
than an error handler. Anything that happens out of the ordinary wakes
the EH thread.
Ideally, I think we really want to have stacked EH as I believe we have
discussed in the past. If we hit an error, we quiesce the device, do device
level EH. If needed, quiesce the device group / port, perform EH. If
necessary, quiesce the entire HBA and perform EH on it.
-Brian
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
next prev parent reply other threads:[~2008-06-02 20:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12124164141515-patch-mail.ibm.com>
2008-06-02 16:08 ` [PATCH 1/1] ipr: Fix HDIO_GET_IDENTITY oops for SATA devices Jeff Garzik
2008-06-02 16:27 ` Brian King
2008-06-02 16:45 ` James Bottomley
2008-06-02 17:43 ` Jeff Garzik
2008-06-02 17:57 ` James Bottomley
2008-06-02 18:11 ` Jeff Garzik
2008-06-02 18:51 ` Brian King
2008-06-02 18:54 ` Jeff Garzik
2008-06-02 19:39 ` James Bottomley
2008-06-02 20:27 ` Brian King [this message]
2008-06-02 19:35 ` James Bottomley
2008-06-02 19:53 ` Alan Cox
2008-07-11 18:37 Brian King
-- strict thread matches above, loose matches on Subject: below --
2008-06-02 14:20 Brian King
2008-06-02 14:20 Brian King
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=4844579E.80005@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=miltonm@bga.com \
--cc=thlin@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).