<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>I tend to agree with George.<br>
<br>
Originally, the TAS bit definition in SPC held sway. As time went
by, Rob succeeded in moving the majority of the TAS requirements
to SAM. Now, SAM repeats the SPC description and greatly
elaborates on it.<br>
<br>
On the other hand, there is no conflict between the SAM and SPC
descriptions, unless one has a minimal understanding of what a
Unit Attention is.<br>
<br>
The years also have not been good to the "(see SAM-5)" reference
at the end of the SPC TAS bit definition. Prior to the invention
of the Note to Entry, this at-the-end format was intended to mean
"everything about this definition is clarified in SAM-5". Now,
it's a dangling oddity.<br>
<br>
With this in mind ...<br>
<br>
The minimalist change is to replace the SPC-5 "(see SAM-5)" with a
new last sentence on the paragraph along the lines of, "SAM-5
describes the effects of the TAS bit in detail." Based on the
notes above, I could consider this to be an editorial change.<br>
<br>
The big-foot change is to remove the "(see SAM-5)" at the end of
the SPC paragraph; begin the paragraph with "As described in
SAM-5, ..."; and replace the two instances of "shall be" with
"are". This is clearly new proposal territory.<br>
<br>
All the best,<br>
<br>
.Ralph<br>
<br>
</tt><br>
<div class="moz-cite-prefix">On 1/26/2016 2:08 PM, Bill Martin-SSI
wrote:<br>
</div>
<blockquote
cite="mid:447B3DEABFA4E54DBC46813E1E007FCE5CD860CA@SSIEXCH-MB3.ssi.samsung.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Segoe UI";
        panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
        {font-family:ArialMT;
        panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">The biggest
confusion here was the apparent opposite meaning of the bit,
but now it is clear that the functionality of the bit was
designed in that when set to one tasks are completed with
TASK ABORTED status and there is no UA. When set to zero
tasks are aborted with no response to the application client
and a UA issued.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Bill Martin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Vice Chair SNIA
Technical Council<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Vice Chair
INCITS T10<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">SSD I/O
Standards </span><span style="font-family:"Segoe
UI","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Samsung
Semiconductor, Inc. </span>
<span style="font-family:"Segoe
UI","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Cell (408)
499-1839</span><span
style="font-size:13.5pt;font-family:"Segoe
UI","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
Black, David [<a class="moz-txt-link-freetext" href="mailto:david.black@emc.com">mailto:david.black@emc.com</a>]
<br>
<b>Sent:</b> Tuesday, January 26, 2016 10:25 AM<br>
<b>To:</b> Bill Martin-SSI;
<a class="moz-txt-link-abbreviated" href="mailto:George.Penokie@avagotech.com">George.Penokie@avagotech.com</a>; Ralph Weber
(<a class="moz-txt-link-abbreviated" href="mailto:roweber@ieee.org">roweber@ieee.org</a>) (<a class="moz-txt-link-abbreviated" href="mailto:roweber@ieee.org">roweber@ieee.org</a>)<br>
<b>Cc:</b> T10 Reflector<br>
<b>Subject:</b> RE: Operation of TAS bit related to Unit
Attention<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m neither
Ralph nor George, but I don’ t see a serious conflict:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- The SAM-5
text is about creating a unit attention condition that is
reported on a *<b>subsequent</b>* command (if it is
reported, see SAM-5 on UA queuing behavior).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">- The SPC-4
text is about how to terminate the *<b>current</b>* command.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">It might be
nice if each chunk of text acknowledged the existence of the
other, but that would be editorial. What have I missed?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,
--David<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a moz-do-not-send="true"
href="mailto:t10-bounces@t10.org">t10-bounces@t10.org</a>
[<a moz-do-not-send="true"
href="mailto:t10-bounces@t10.org">mailto:t10-bounces@t10.org</a>]
<b>On Behalf Of </b>Bill Martin-SSI<br>
<b>Sent:</b> Tuesday, January 26, 2016 11:11 AM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:George.Penokie@avagotech.com">George.Penokie@avagotech.com</a>;
Ralph Weber (<a moz-do-not-send="true"
href="mailto:roweber@ieee.org">roweber@ieee.org</a>)
(<a moz-do-not-send="true"
href="mailto:roweber@ieee.org">roweber@ieee.org</a>)<br>
<b>Cc:</b> T10 Reflector; Stefanus (Fnu) Stefanus-SSI<br>
<b>Subject:</b> [T10] Operation of TAS bit related to
Unit Attention<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ralph & George:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is a conflict between SAM-5 and
SPC-4 on the meaning of the TAS bit.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">SAM-5r21 states:<o:p></o:p></p>
<p class="MsoNormal">If the TAS bit is set to zero in the
Control mode page (see SPC-4), then the device server
creates this unit attention condition for each I_T nexus
that had command(s) aborted other than the I_T nexus that
delivered the command. If the TAS bit is set to one in the
Control mode page (see SPC-4), then the device server does
not create this unit attention condition.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">SPC-4r08 states:<o:p></o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:10.0pt;font-family:"ArialMT","sans-serif"">A
task aborted status (</span><span
style="font-size:8.0pt;font-family:"ArialMT","sans-serif"">TAS</span><span
style="font-size:10.0pt;font-family:"ArialMT","sans-serif"">)
bit set to zero specifies that aborted commands shall be
terminated by the device server without any response to
the application client. A
</span><span
style="font-size:8.0pt;font-family:"ArialMT","sans-serif"">TAS
</span>
<span
style="font-size:10.0pt;font-family:"ArialMT","sans-serif"">bit
set to one specifies that commands aborted by the actions
of an I_T nexus other than the I_T nexus on which the
command was received shall be completed with TASK ABORTED
status (see SAM-5).<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:10.0pt;font-family:"ArialMT","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:10.0pt;font-family:"ArialMT","sans-serif"">Which
was the intended meaning of this bit?<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:10.0pt;font-family:"ArialMT","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span
style="font-size:10.0pt;font-family:"ArialMT","sans-serif"">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Bill Martin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Vice Chair
SNIA Technical Council<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Vice Chair
INCITS T10<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">SSD I/O
Standards </span><span style="font-family:"Segoe
UI","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Samsung
Semiconductor, Inc. </span>
<span style="font-family:"Segoe
UI","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Cell (408)
499-1839</span><span
style="font-size:13.5pt;font-family:"Segoe
UI","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="text-autospace:none"><o:p> </o:p></p>
</div>
</div>
</blockquote>
<br>
</body>
</html>