From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: brking@linux.vnet.ibm.com
Cc: Jeff Garzik <jeff@garzik.org>,
linux-scsi@vger.kernel.org, thlin@linux.vnet.ibm.com,
linux-ide@vger.kernel.org, miltonm@bga.com,
Tejun Heo <htejun@gmail.com>
Subject: Re: [PATCH 1/1] ipr: Fix HDIO_GET_IDENTITY oops for SATA devices
Date: Mon, 02 Jun 2008 11:45:24 -0500 [thread overview]
Message-ID: <1212425124.3369.20.camel@localhost.localdomain> (raw)
In-Reply-To: <48441F82.6060706@linux.vnet.ibm.com>
On Mon, 2008-06-02 at 11:27 -0500, Brian King wrote:
> There is also the issue of HBA queue limits. Since each SATA rphy uses
> its
> own SCSI host, we lost host queue limit enforcement. I've implemented
> a
> request_limit in ipr in order to solve this for ipr, but this really
> does not scale well to lots of SATA devices, so we would probably need
> queue groups at the block level before moving libsas to the new API.
But this is the point that principally illustrates the problems. We
really need one SCSI host per physical device, not per phy because most
multi-phy devices have a hard per device queue limit.
The problems seem to come at us from the 1:1 relationship between a
'port' and a host in libata. Is there no way we can perhaps recast what
we think of as a phy as what libata thinks of as a link and thus keep us
at one host per actual physical device?
James
next prev parent reply other threads:[~2008-06-02 16:45 UTC|newest]
Thread overview: 14+ 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 [this message]
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
2008-06-02 19:35 ` James Bottomley
2008-06-02 19:53 ` Alan Cox
2008-06-02 14:20 Brian King
-- strict thread matches above, loose matches on Subject: below --
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=1212425124.3369.20.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=brking@linux.vnet.ibm.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).