PHY numbering within a Wide Port

Sheffield, Robert L robert.l.sheffield at intel.com
Mon Aug 29 10:59:48 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Sheffield, Robert L" <robert.l.sheffield at intel.com>
*
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5ACC3.72F5B8F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

An earlier version of SAS-1.1 was a bit ambiguous on the point and
opened a possible interpretation that phys would have to be numbered
sequentially within a wide port. But it appears to have been clarified
in this version that reporting of phys is done on a per-device basis,
with no implicit or explicit association between the phys reported and
the ports which map to those phys other than the reported SAS address
associated with the phy.
=20
Recent changes have also allowed the PHY VACANT SMP response to support
recognition of a phy which is numbered, but not attached to anything,
and so is not relevant in the current configuration.=20
=20
References:

4.2.7 Phy identifiers

Each SAS phy and expander phy shall be assigned an identifier that is
unique within the SAS device and/or
expander device. The phy identifier is used for management functions
(see 10.4).
Phy identifiers shall be greater than or equal to 00h and less than =
80h,
and should be numbered starting with
00h. In an expander device or in a SAS device containing an SMP target
port, phy identifiers shall be less than
the value of the NUMBER OF PHYS field in the SMP REPORT GENERAL =
function
(see 10.4.3.3). In a SAS
device containing an SSP target port, phy identifiers shall be less =
than
the value of the NUMBER OF PHYS field
in the Protocol-Specific Port mode page for SAS SSP - Phy Control And
Discover subpage (see 10.2.7.2.3).

10.2.7.2.3 Protocol-Specific Port mode page - Phy Control And Discover
subpage
...

A SAS phy mode descriptor shall be included for each phy in the SAS
target device, not just the SAS target
port, starting with the lowest numbered phy and ending with the highest
numbered phy.

The last paragraph was changed in the latest revision to clarify phys
are reported on a target device basis, not a port basis.
=20
Bob Sheffield
Intel

  _____ =20

From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Bill
Martin
Sent: Monday, August 29, 2005 6:26 AM
To: t10 at t10.org
Subject: PHY numbering within a Wide Port



>From SAS 1.1, it is required that a device have all of its PHYs =
numbered
consecutively from 1 to the maximum number of PHYs.  Is there any
requirement that the PHYs in a wide port be consecutively numbered.  I
do not currently find any restrictions on the numbering of PHYs in a
wide port.

=20

Thanks,

=20

Bill Martin
Sr. Principal Engineer
Standards and Interoperability
Sierra Logic, Inc.
916 772-3658

916 765-6875 (Cell)
bill_martin at sierralogic.com

=20


------_=_NextPart_001_01C5ACC3.72F5B8F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>

<META content=3D"MSHTML 6.00.2900.2627" =
name=3DGENERATOR><o:SmartTagType=20
name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D708424917-29082005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>An earlier version of SAS-1.1 was a bit =
ambiguous on the=20
point and opened a possible interpretation that phys would have to be =
numbered=20
sequentially within a wide port. But it appears to have been clarified =
in this=20
version that reporting of phys is done on a per-device basis, with no =
implicit=20
or explicit association between the phys reported and the ports which =
map to=20
those phys other than the reported SAS address associated with the=20
phy.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D708424917-29082005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D708424917-29082005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Recent changes have also allowed the PHY =
VACANT SMP=20
response to support recognition of a phy which is numbered, but not =
attached to=20
anything, and so is not relevant in the current configuration.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D708424917-29082005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D708424917-29082005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>References:</FONT></SPAN></DIV><SPAN=20
class=3D708424917-29082005><B><FONT face=3DArial size=3D2>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV dir=3Dltr align=3Dleft>4.2.7 Phy =
identifiers</DIV></B></FONT><FONT face=3DArial=20
  size=3D2>
  <DIV align=3Dleft>Each SAS phy and expander phy shall be assigned an =
identifier=20
  that is unique within the SAS device and/or</DIV>
  <DIV align=3Dleft>expander device. The phy identifier is used for =
management=20
  functions (see 10.4).</DIV>
  <DIV align=3Dleft>Phy identifiers shall be greater than or equal to =
00h and less=20
  than 80h, and should be numbered starting with</DIV>
  <DIV align=3Dleft>00h. In an expander device or in a SAS device =
containing an=20
  SMP target port, phy identifiers shall be less than</DIV>
  <DIV align=3Dleft>the value of the </FONT><FONT face=3DArial =
size=3D1>NUMBER OF PHYS=20
  </FONT><FONT face=3DArial size=3D2>field in the SMP REPORT GENERAL =
function (see=20
  10.4.3.3). In a SAS</DIV>
  <DIV align=3Dleft>device containing an SSP target port, phy =
identifiers shall be=20
  less than the value of the </FONT><FONT face=3DArial size=3D1>NUMBER =
OF PHYS=20
  </FONT><FONT face=3DArial size=3D2>field</FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial size=3D2>in the =
Protocol-Specific Port mode=20
  page for SAS SSP - Phy Control And Discover subpage (see=20
  10.2.7.2.3).</FONT></DIV></BLOCKQUOTE>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV dir=3Dltr><FONT face=3DArial size=3D2><STRONG>10.2.7.2.3 =
Protocol-Specific Port=20
  mode page - Phy Control And Discover subpage</STRONG></FONT></DIV>
  <DIV><SPAN class=3D708424917-29082005><FONT face=3DArial=20
  size=3D2><STRONG>...</STRONG></FONT></SPAN></DIV><SPAN=20
  class=3D708424917-29082005><FONT face=3DArial size=3D2>
  <DIV>A SAS phy mode descriptor shall be included for each phy in the =
SAS=20
  target device, not just the SAS target</DIV>
  <DIV>port, starting with the lowest numbered phy and ending with the =
highest=20
  numbered phy.</DIV></BLOCKQUOTE>
<UL dir=3Dltr style=3D"MARGIN-RIGHT: 0px"></FONT></SPAN></SPAN></UL>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D708424917-29082005>The=20
last paragraph was changed in the latest revision to clarify phys are =
reported=20
on a target device basis, not a port basis.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D708424917-29082005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D708424917-29082005>Bob=20
Sheffield</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D708424917-29082005>Intel</SPAN></FONT></DIV>
<DIV><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> owner-t10 at t10.org=20
[mailto:owner-t10 at t10.org] <B>On Behalf Of </B>Bill =
Martin<BR><B>Sent:</B>=20
Monday, August 29, 2005 6:26 AM<BR><B>To:</B> =
t10 at t10.org<BR><B>Subject:</B> PHY=20
numbering within a Wide Port<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">From SAS 1.1, it is =
required that a=20
device have all of its PHYs numbered consecutively from 1 to the =
maximum number=20
of PHYs.&nbsp; Is there any requirement that the PHYs in a wide port be =

consecutively numbered.&nbsp; I do not currently find any restrictions =
on the=20
numbering of PHYs in a wide port.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><st1:PersonName w:st=3D"on"><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Bill=20
Martin</SPAN></FONT></st1:PersonName><BR><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sr. Principal =
Engineer<BR>Standards=20
and Interoperability<BR>Sierra Logic, Inc.<BR>916=20
772-3658</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">916 765-6875=20
(Cell)<BR>bill_martin at sierralogic.com<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV></BODY></HTML>

------_=_NextPart_001_01C5ACC3.72F5B8F0--





More information about the T10 mailing list