|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Emailing: msg10855.txt
<!-- MHonArc v2.4.9 --> <!--X-Subject: RE: iSCSI: advancing CmdSN after a command retry rule --> <!--X-From-R13: cng_gunyreNntvyrag.pbz --> <!--X-Date: Mon, 17 Jun 2002 12:25:20 -0400 (EDT) --> <!--X-Message-Id: 1BEBA5E8600DD4119A50009027AF54A00C891386@axcs04.cos.agilent.com --> <!--X-Content-Type: multipart/mixed --> <!--X-Head-End--> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML//EN"> <html> <head> <title>RE: iSCSI: advancing CmdSN after a command retry rule</title> <link rev="made" href="mailto:pat_thaler@agilent.com";> </head> <BODY bgcolor=#FFFFFF background="/mailinglists/ips/images/black-side.gif" LEFTMARGIN="0" TOPMARGIN="0" MARGINHEIGHT="0" MARGINWIDTH="0"> <!--X-Body-Begin--> <!--X-User-Header--> <img SRC="/mailinglists/ips/images/redbar_flag4.gif" height=41 width=640> <p> <TABLE BORDER=0 CELLSPACING=10 CELLPADDING=0 WIDTH="640"> <TR> <TD VALIGN=TOP WIDTH="155"> <table width="100"> <tr><td> <B><FONT FACE="Arial,Helvetica" COLOR="#FFFFFF" SIZE=-1>SORT BY:</FONT></B> <P><a href="maillist.html"><B><FONT FACE="Arial,Helvetica" COLOR="#FFFFFF" SIZE=-1> LIST ORDER</FONT></B></a> <br><a href="threads.html"><B><FONT FACE="Arial,Helvetica" COLOR="#FFFFFF" SIZE=-1> THREAD</FONT></B></a> <br><a href="author.html"><B><FONT FACE="Arial,Helvetica" COLOR="#FFFFFF" SIZE=-1 >AUTHOR</FONT></B></a> <br><a href="subject.html"><B><FONT FACE="Arial,Helvetica" COLOR="#FFFFFF" SIZE=-1 >SUBJECT</FONT></B></a> </td></tr> <tr><td valign=bottom> <p><br><B><FONT FACE="Arial,Helvetica"><FONT COLOR="#FFFFFF"><FONT SIZE=-1>SEARCH</FONT> </FONT></FONT></B> </td></tr> <tr><td valign=top> <FORM method="post" action="/cgi-bin/htsearchIPS" > <INPUT type="text" name="words" size=12> <input type="hidden" name="method" value="all"> <input type="hidden" name="format" value="short"> <input type="hidden" name="sort" value="score"> <input type="hidden" name="config" value="htdig"> <input type="hidden" name="restrict" value=""> <input type="hidden" name="exclude" value=""> </FORM> <p> <a href="http://www.ece.cmu.edu/~ips";><B><FONT FACE="Arial,Helvetica"><FONT COLOR="#FFFFFF"><FONT SIZE=-1> IPS HOME </FONT></FONT></FONT></B></a> </td></tr> </table> <td valign=top width="465"> <ul> <!--X-User-Header-End--> <!--X-TopPNI--> <hr> [<a href="msg10854.html">Date Prev</a>][<a href="msg10856.html">Date Next</a>][<a href="msg10849.html">Thread Prev</a>][<a href="msg10854.html">Thread Next</a>][<a href="maillist.html#10855">Date Index</a>][<a href="thrd109.html#10855">Thread Index</a>] <!--X-TopPNI-End--> <!--X-MsgBody--> <!--X-Subject-Header-Begin--> <h1>RE: iSCSI: advancing CmdSN after a command retry rule</h1> <hr> <!--X-Subject-Header-End--> <!--X-Head-of-Message--> <ul> <li><strong>To</strong>: <strong><A HREF="mailto:Julian_Satran@il.ibm.com";>Julian_Satran@il.ibm.com</A>, <A HREF="mailto:pat_thaler@agilent.com";>pat_thaler@agilent.com</A></strong></li> <li><strong>Subject</strong>: <strong>RE: iSCSI: advancing CmdSN after a command retry rule</strong></li> <li><strong>From</strong>: <strong><A HREF="mailto:pat_thaler@agilent.com";>pat_thaler@agilent.com</A></strong></li> <li>Date: Mon, 17 Jun 2002 10:25:14 -0600</li> <li>Cc: <A HREF="mailto:ips@ece.cmu.edu";>ips@ece.cmu.edu</A></li> <li>Content-Type: multipart/mixed;boundary="----=_NextPartTM-000-82f14adb-820c-11d6-ac7f-009027aa5b50"</li> <li>Sender: <A HREF="mailto:owner-ips@ece.cmu.edu";>owner-ips@ece.cmu.edu</A></li> </ul> <!--X-Head-of-Message-End--> <!--X-Head-Body-Sep-Begin--> <hr> <!--X-Head-Body-Sep-End--> <!--X-Body-of-Message--> <DIV><SPAN class=880062316-17062002><FONT face=Arial size=2>Julian,</FONT></SPAN></DIV> <DIV><SPAN class=880062316-17062002><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=880062316-17062002><FONT face=Arial size=2>Thanks. That still leaves the problem that there is no definition of when a connection is "operational" but that could be added to the last call issues.</FONT></SPAN></DIV> <DIV><SPAN class=880062316-17062002><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=880062316-17062002><FONT face=Arial size=2>Pat</FONT></SPAN></DIV> <DIV><SPAN class=880062316-17062002><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Julian Satran [mailto:Julian_Satran@il.ibm.com]<BR><B>Sent:</B> Saturday, June 15, 2002 9:27 AM<BR><B>To:</B> THALER,PAT (A-Roseville,ex1)<BR><B>Cc:</B> ips@ece.cmu.edu<BR><B>Subject:</B> Re: iSCSI: advancing CmdSN after a command retry rule<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>Pat,</FONT> <BR><BR><FONT face=sans-serif size=2>If the connection went through a "restart" (login with the same CID) then the "cleaning" is also not needed.</FONT> <BR><FONT face=sans-serif size=2>Your text modified as follows is acceptable:</FONT> <BR><BR><FONT face="Courier New" size=3>If an initiator issues a command retry for a command with CmdSN R on</FONT> <BR><FONT face="Courier New" size=3>a connection when the session CmdSN register is Q, it MUST NOT advance the CmdSN past R + 2**31 -1 unless the connection is no longer operational, or the connection has been reinstated (see Section 4.3.4 Connection reinstatement), or a non-immediate command with CmdSN equal or greater than Q was issued on the same connection and the reception of the command is acknowledged by the target (see Section 8.4 Command Retry and Cleaning Old Command Instances).</FONT> <BR><BR><FONT face=sans-serif size=2>Thanks,</FONT> <BR><FONT face=sans-serif size=2>Julo</FONT> <BR><BR><BR><BR> <TABLE width="100%"> <TBODY> <TR vAlign=top> <TD> <TD><FONT face=sans-serif size=1><B>"THALER,PAT (A-Roseville,ex1)" <pat_thaler@agilent.com></B></FONT> <P><FONT face=sans-serif size=1>06/15/2002 03:39 AM</FONT> <BR><FONT face=sans-serif size=1>Please respond to "THALER,PAT (A-Roseville,ex1)"</FONT> <BR></P> <TD><FONT face=Arial size=1> </FONT><BR><FONT face=sans-serif size=1> To: Julian Satran/Haifa/IBM@IBMIL, ips@ece.cmu.edu</FONT> <BR><FONT face=sans-serif size=1> cc: </FONT> <BR><FONT face=sans-serif size=1> Subject: iSCSI: advancing CmdSN after a command retry rule</FONT> <BR><BR><FONT face=Arial size=1> </FONT></TR></TBODY></TABLE><BR><BR><FONT face="Courier New" size=2>Julian,<BR><BR>I'm having a little trouble understanding this text near the end of 2.2.2.1:<BR><BR>If an initiator issues a command retry for a command with CmdSN R on<BR>a connection when the session CmdSN register is Q, it MUST NOT<BR>advance the CmdSN past R + 2**31 -1 unless a different non-immediate<BR>command with CmdSN equal or greater than Q was issued on the same<BR>connection if the connection is still operational, and the reception<BR>of the command is acknowledged by the target (see Section 8.4 Command<BR>Retry and Cleaning Old Command Instances). The second non-immediate<BR>command when sent, MUST be sent in-order after the retried<BR>command on the same connection.<BR><BR>What does "different" mean in a different non-immediate command with CmdSN equal or greater than Q"? Isn't any command with a new CmdSN because it has a new CmdSN? <BR><BR>What is the purpose of "if the connection is still operational"? If a new command is issued on the connection it must still be operational. Perhaps it was intended to mean that if the connection was not operational then CmdSN can be advanced past the limit without this requirement being met. <BR><BR>There doesn't seem to be any definition of when a connection is "operational". Does the connection leave the operational state when it leaves S5 or is it when it has returned to S1?<BR><BR>Does "second non-immediate command" mean the command sent on this connection with CmdSN equal or greater than Q? Other commands with Q <= CmdSN < R + 2**31 - 1 may be sent on other connections, so the second command is the second command on this connection, right?<BR><BR>It isn't clear what the last sentence was intended to do since any command sent before the retry would advance Q so inherently any command sent after the retry with a new CmdSN must be in-order after the retry. <BR><BR>I suggest the following text plus clarification of the meaning of operational for a connection:<BR>"If an initiator issues a command retry for a command with CmdSN R on<BR>a connection when the session CmdSN register is Q, it MUST NOT<BR>advance the CmdSN past R + 2**31 -1 unless the connection is no longer operational or a non-immediate command with CmdSN equal or greater than Q was issued on the same<BR>connection and the reception of the command is acknowledged by the target (see Section 8.4 Command Retry and Cleaning Old Command Instances). <BR><BR>Pat <BR></FONT><BR><BR> <!--X-Body-of-Message-End--> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <hr> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <ul> <li>Prev by Date: <strong><a href="msg10854.html">iSCSI: Is the TargetPortalGroupTag key allowed on a discovery session?</a></strong> </li> <li>Next by Date: <strong><a href="msg10856.html">iSCSI 0.13 vs. iSCSI Plugfest</a></strong> </li> <li>Prev by thread: <strong><a href="msg10849.html">Re: iSCSI: advancing CmdSN after a command retry rule</a></strong> </li> <li>Next by thread: <strong><a href="msg10854.html">iSCSI: Is the TargetPortalGroupTag key allowed on a discovery session?</a></strong> </li> <li>Index(es): <ul> <li><a href="maillist.html#10855"><strong>Date</strong></a></li> <li><a href="thrd109.html#10855"><strong>Thread</strong></a></li> </ul> </li> </ul> <!--X-BotPNI-End--> <!--X-User-Footer--> </ul> <p> <hr> <strong> <a href="http://sip.pdl.cs.cmu.edu";>Home</a> </strong> <p> <address> Last updated: Mon Jun 17 13:18:48 2002<br> 10859 messages in chronological order<br> </address> </TABLE> <!--X-User-Footer-End--> </body> </html>
Home Last updated: Wed Jun 19 14:19:03 2002 10891 messages in chronological order |