From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: Christoph Hellwig <hch@lst.de>,
jejb@steeleye.com, Eric.Moore@lsil.com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/4] sas: add flag for locally attached PHYs
Date: Wed, 19 Oct 2005 15:37:54 -0400 [thread overview]
Message-ID: <4356A092.6060504@adaptec.com> (raw)
In-Reply-To: <43569D5D.1000801@adaptec.com>
On 10/19/05 15:24, Luben Tuikov wrote:
> On 10/19/05 14:01, Christoph Hellwig wrote:
>
>>Add a flag to mark a PHY as attached to the HBA as opposed to beeing on
>>an expander. This is needed because various features are only supported
>>on those. This is a crude hack, the proper fix would be to use
>>different classes for host-attached vs expander phys. I'm looking into
>>that.
>
>
> The phy isn't quite "attached" -- i.e. at software level you do not
> care about that. At least I've never heard anyone (not of "the community")
> say that a phy is "attached".
>
> You don't need to represent that. While you can, you completely do not
> need to do it. All you should care about is the _port_. Take a look
> at SAS section 4.
>
> Also take a look at:
> drivers/scsi/sas/sas_phy.c,
> drivers/scsi/sas/sas_port.c and
> drivers/scsi/sas/sas_discover.c .
>
> Storage GUI applications can read the expander configuration using SMP
> and show this as I've shown in Announcement 1 here:
> http://marc.theaimsgroup.com/?l=linux-scsi&m=112629509826900&w=2
And Announcement 2 (more specifically using the user space configuration
utility program "expander_conf.c"):
http://marc.theaimsgroup.com/?l=linux-scsi&m=112629509318354&w=2
Luben
--
http://linux.adaptec.com/sas/
http://www.adaptec.com/sas/
> All you should care about is the _local_ phys since those are
> under your control, and the port formed.
>
> Luben
next prev parent reply other threads:[~2005-10-19 19:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 18:01 [PATCH 1/4] sas: add flag for locally attached PHYs Christoph Hellwig
2005-10-19 19:24 ` Luben Tuikov
2005-10-19 19:37 ` Luben Tuikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-19 20:08 Moore, Eric Dean
2005-10-19 21:00 ` Luben Tuikov
2005-10-20 14:11 ` Christoph Hellwig
2005-10-20 15:29 ` Luben Tuikov
2005-10-20 15:49 ` Christoph Hellwig
2005-10-20 16:08 ` Luben Tuikov
2005-10-20 15:25 Moore, Eric Dean
2005-10-20 15:55 ` Luben Tuikov
2005-10-20 16:01 ` Christoph Hellwig
2005-10-20 16:51 ` Luben Tuikov
2005-10-20 17:03 ` Christoph Hellwig
2005-10-20 17:22 ` Arjan van de Ven
2005-10-20 20:10 ` Luben Tuikov
2005-10-21 8:16 ` Arjan van de Ven
2005-10-20 20:02 ` Luben Tuikov
2005-10-21 0:01 ` Andrew Patterson
2005-10-21 9:06 ` Arjan van de Ven
2005-10-21 17:05 ` Andrew Patterson
2005-10-21 17:18 ` Arjan van de Ven
2005-10-21 18:57 ` Luben Tuikov
2005-10-21 17:32 ` Luben Tuikov
2005-10-21 1:50 ` Douglas Gilbert
2005-10-21 2:16 ` Jeff Garzik
2005-10-21 3:25 ` Douglas Gilbert
2005-10-21 18:04 ` Luben Tuikov
2005-10-20 15:45 Moore, Eric Dean
2005-10-20 16:16 ` Luben Tuikov
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=4356A092.6060504@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=Eric.Moore@lsil.com \
--cc=hch@lst.de \
--cc=jejb@steeleye.com \
--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 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.