From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: brking@linux.vnet.ibm.com, 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 13:43:08 -0400 [thread overview]
Message-ID: <4844312C.7010403@garzik.org> (raw)
In-Reply-To: <1212425124.3369.20.camel@localhost.localdomain>
James Bottomley wrote:
> 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?
It's difficult to do that universally, but OTOH it would be quite
reasonable to do that for modern SATA controllers, leaving the older
master/slave controllers as one-host-per-port.
I've been wanting to do that for a while, even.
The main thing holding me back is not any technical issue, but desire to
avoid breakage caused by abrupt topology change.
Jeff
next prev parent reply other threads:[~2008-06-02 17:43 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 [this message]
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-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=4844312C.7010403@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=brking@linux.vnet.ibm.com \
--cc=htejun@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.