SAS 1.1 Protocol-Specific Logical Unit mode page question

Bill Martin bill_martin at sierralogic.com
Wed Aug 3 20:01:20 PDT 2005


* From the T10 Reflector (t10 at t10.org), posted by:
* "Bill Martin" <bill_martin at sierralogic.com>
*
This is a multi-part message in MIME format.

------=_NextPart_000_00D7_01C59866.1E969B80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

In Protocol-Specific Logical Unit mode page for SAS SSP, there is a
field called "Transport Layer Retries".  There is no indication of a
requirement for this field to be changeable.  While it is possible to
determine if it is changeable in a particular implementation, If it is
not changeable there is no mechanism documented to allow an initiator to
stop the target from performing transport layer retries.

 

Was the intention that this field be required to be changeable?

 

 

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

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

 


------=_NextPart_000_00D7_01C59866.1E969B80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>

<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>In =
Protocol-Specific Logical
Unit mode page for SAS SSP, there is a field called "Transport =
Layer
Retries".&nbsp; There is no indication of a requirement for this =
field to be
changeable.&nbsp; While it is possible to determine if it is changeable =
in a
particular implementation, If it is not changeable there is no =
mechanism documented
to allow an initiator to stop the target from performing transport =
layer
retries.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Was the intention =
that this
field be required to be changeable?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Bill Martin<br>
Sr. Principal Engineer<br>
Standards and Interoperability<br>
Sierra Logic, Inc.<br>
916 772-3658</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>916 765-6875 (Cell)<br>
bill_martin at sierralogic.com</span></font><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></=
p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_00D7_01C59866.1E969B80--





More information about the T10 mailing list