From: Douglas Gilbert <dgilbert@interlog.com>
To: Ravi Shankar <ravi.v.shankar@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: mpt2sas: /sysfs sas_address entries do not show individual port sas addresses.
Date: Thu, 18 Aug 2011 15:52:24 -0400 [thread overview]
Message-ID: <4E4D6D78.6040106@interlog.com> (raw)
In-Reply-To: <4E4D529F.9090908@oracle.com>
On 11-08-18 01:57 PM, Ravi Shankar wrote:
>
>>
>>
>> Do you know a reason why it is not preferably for every
>> phy on a SAS HBA to respond with the same SAS address?
>>
>>
>> As a practical matter a SAS HBA needs a single SAS address,
>> preferably printed on the board or its box. Then if you
>> manage to wipe its SAS address (e.g. by erasing its flash
>> to move from IR to IT firmware) then you know which SAS
>> address to re-instate :-)
>>
> HBA SAS phy could have same SAS address when they are directly connected.
> however when connected to expanders, each logical port/phy need unique SAS
> address.
No.
SAS HBAs and expanders should always be trying to maximize
the width of a link. By definition all physical ** phys on an
expander should (must) have the same SAS address. So if
you connect 5 phys from a SAS HBA to the same expander (and
the HBA supports links wider than 4 phys) then those
5 HBA phys should have the same SAS address. Those 5 HBA
phys then form a SCSI port.
Just tested a triangular arrangement: a LSI SAS-2 HBA
(9212-4i4e) connected to one SAS-2 expander (4 phy wide link)
and one SAS-1 expander (narrow link). And the expanders
where connected to each other. Two disks were connected
to the SAS-2 expander.
Both expanders reported the same SAS address for the
5 HBA attached phys. You might argue that is two
separate SCSI initiator ports with the same port
identifier (SAS address) in the same SAS domain.
Anyway there was an interesting difference between the HBA's
BIOS and Linux (lk 3.0.3): the BIOS reported those two
disks twice while Linux only reported them once. That seems
to suggest that the BIOS set up the routing table in the
SAS-1 expander while Linux did not. smp_discover in Linux
confirms that the SAS-1 expander's route table was not set up.
The trouble with testing is that is raises more questions
than it supplies answers.
SAS disks have two phys which are typically given two
different SAS addresses. This stops them forming a wide link
if, for example, they were both connected to the same
expander. Typically the two SAS disk phys would be connected
to different expanders for redundancy. However if the
interest was speed (e.g. with a SAS SSD) then both the
disk phys might be given the same SAS address.
** SAS-2 expanders often have an integrated SES target
on a virtual phy in the expander chip, and that
virtual phy has a different SAS address.
Doug Gilbert
P.S. Why is my post cc-ing to "unlisted-recipients:;"
next prev parent reply other threads:[~2011-08-18 20:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 10:42 mpt2sas: /sysfs sas_address entries do not show individual port sas addresses Benjamin ESTRABAUD
2011-08-17 15:35 ` Douglas Gilbert
2011-08-17 15:50 ` Benjamin ESTRABAUD
2011-08-18 17:57 ` Ravi Shankar
2011-08-18 19:52 ` Douglas Gilbert [this message]
2011-08-19 12:30 ` Benjamin ESTRABAUD
2011-08-19 14:58 ` Douglas Gilbert
2011-08-19 17:49 ` Benjamin ESTRABAUD
2011-08-19 19:06 ` Ravi Shankar
2011-08-21 1:05 ` Douglas Gilbert
2011-08-23 19:39 ` Ravi Shankar
2011-08-24 14:12 ` Benjamin ESTRABAUD
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=4E4D6D78.6040106@interlog.com \
--to=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ravi.v.shankar@oracle.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