From: James Bottomley <James.Bottomley@SteelEye.com>
To: Christoph Hellwig <hch@lst.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] SAS transport class
Date: Fri, 09 Sep 2005 09:35:36 -0500 [thread overview]
Message-ID: <1126276536.4799.5.camel@mulgrave> (raw)
In-Reply-To: <20050909142250.GA13136@lst.de>
On Fri, 2005-09-09 at 16:22 +0200, Christoph Hellwig wrote:
> In addition to the basic SCSI core objects this transport class introduces
> two additional intermediate objects: The SAS PHY as represented by struct
> sas_phy defines an "outgoing" PHY on a SAS HBA or Expander, and the SAS
> remote PHY represented by struct sas_rphy defines an "incoming" PHY on a
> SAS Expander or end device. Note that this is purely a software concept, the
> underlying hardware for a PHY and a remote PHY is the exactly the same.
My only real comment is that an outgoing PHY should probably exist in a
separate class because that concept is common to SATA, so the class
should be shareable between sas/sata.
What you call a sas_rphy, when it's an expander input is the thing we're
going to want to attach an SMP tap to for the management tools
(eventually).
> I think this submission is ready for 2.6.14, but additional comments are
> of course very welcome.
Hmm ... OK ... we can try this in rc-fixes at first.
James
next prev parent reply other threads:[~2005-09-09 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 14:22 [PATCH] SAS transport class Christoph Hellwig
2005-09-09 14:35 ` James Bottomley [this message]
2005-09-09 14:38 ` Christoph Hellwig
2005-09-09 23:38 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-09-06 14:24 James.Smart
2005-09-06 13:40 James.Smart
2005-09-06 14:00 ` Christoph Hellwig
2005-09-06 16:00 ` Stefan Richter
2005-09-04 23:50 Christoph Hellwig
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=1126276536.4799.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
/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