Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id h1L039e08233 for ips-outgoing; Thu, 20 Feb 2003 19:03:09 -0500 (EST) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h1L035W08224 for ; Thu, 20 Feb 2003 19:03:05 -0500 (EST) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id A746414CFA; Thu, 20 Feb 2003 17:03:03 -0700 (MST) Received: from axcsbh2.cos.agilent.com (axcsbh2.cos.agilent.com [130.29.152.144]) by relcos2.cos.agilent.com (Postfix) with SMTP id 71E3261B; Thu, 20 Feb 2003 17:03:03 -0700 (MST) Received: from 130.29.152.144 by axcsbh2.cos.agilent.com (InterScan E-Mail VirusWall NT); Thu, 20 Feb 2003 17:03:01 -0700 Received: by axcsbh2.cos.agilent.com with Internet Mail Service (5.5.2653.19) id <1RKK7573>; Thu, 20 Feb 2003 17:03:01 -0700 Message-ID: <1BEBA5E8600DD4119A50009027AF54A010F37CB0@axcs04.cos.agilent.com> From: pat_thaler@agilent.com To: DYoung@Brocade.COM, blandry@crossroads.com, nramas@windows.microsoft.com Cc: ips@ece.cmu.edu Subject: RE: iSCSI: Data In PDU with S bit set Date: Thu, 20 Feb 2003 17:02:59 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-d24540d5-4526-11d7-ac8c-009027aa5b50" Sender: owner-ips@ece.cmu.edu Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------=_NextPartTM-000-d24540d5-4526-11d7-ac8c-009027aa5b50 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2D93C.9882CF90" ------_=_NextPart_001_01C2D93C.9882CF90 Content-Type: text/plain; charset="iso-8859-1" Dennis, You appear to have misunderstood the question. Lakshmi wasn't asking about whether a separate SCSI Response PDU could be used instead of setting the S bit. The question was about whether a SCSI Response PDU could be sent fora a command when the S bit had been set in the Data-In PDU. See Eddy's response. Sending the status completes the task. It doesn't matter whether the status was sent with phase collapse by setting the S bit in a Data-In PDU or with separate SCSI Response PDU. iSCSI doesn't need to add anything about this. Processing status belongs to SAM. Pat -----Original Message----- From: Dennis Young [mailto:DYoung@Brocade.COM] Sent: Wednesday, February 19, 2003 6:48 PM To: 'Buck Landry'; Lakshmi Ramasubramanian Cc: ips@ece.cmu.edu Subject: RE: iSCSI: Data In PDU with S bit set In section 10.7 (draft 20): Status can accompany the last Data-in PDU if the command did not end with an exception (i.e., the status is "good status" - GOOD, CONDITION MET or INTERMEDIATE CONDITION MET). The presence of status (and of a residual count) is signaled though the S flag bit. Although targets MAY choose to send even non-exception status in separate responses, initiators MUST support non-exception status in Data-In PDUs. Based on the last sentence of the above paragraph, the initiator has to be able to handle both cases, while the target has the option to not send a separate response if there is no exception. -Dennis >-----Original Message----- >From: Buck Landry [ mailto:blandry@crossroads.com ] >Sent: Wednesday, February 19, 2003 5:18 PM >To: Lakshmi Ramasubramanian >Cc: ips@ece.cmu.edu; Julian_Satran@il.ibm.com >Subject: RE: iSCSI: Data In PDU with S bit set > > >Well, I don't see any explicit text (too bad), but.. > >3.5.1.5 "the last SCSI Data-in PDU passed for a command may >also contain the status if the status indicates termination >with no exceptions (no sense or response involved)" > >.. implies (maybe just to me) that the SCSI task is terminated >by a Data-In PDU w/S bit set. A further response to a >terminated task would be inappropriate methinks, unless you >want to start talking about error recovery.. > >Hope this helps, --buck > > -----Original Message----- >From: Lakshmi Ramasubramanian [ mailto:nramas@windows.microsoft.com ] >Sent: Wednesday, February 19, 2003 4:55 PM >To: ips@ece.cmu.edu >Subject: iSCSI: Data In PDU with S bit set > > >If the target sends a Data In PDU with S bit set, >can it also send a SCSI Response PDU for the same command? > >If the answer is no, there is no text in the spec that >says a target should not send scsi response PDU. > >thanks! > -lakshmi > > > > > ------_=_NextPart_001_01C2D93C.9882CF90 Content-Type: text/html; charset="iso-8859-1" RE: iSCSI: Data In PDU with S bit set
Dennis,
 
You appear to have misunderstood the question. Lakshmi wasn't asking about whether a separate SCSI Response PDU could be used instead of setting the S bit. The question was about whether a SCSI Response PDU could be sent fora a command when the S bit had been set in the Data-In PDU.
 
See Eddy's response. Sending the status completes the task. It doesn't matter whether the status was sent with phase collapse by setting the S bit in a Data-In PDU or with separate SCSI Response PDU. iSCSI doesn't need to add anything about this. Processing status belongs to SAM.
 
Pat
 
-----Original Message-----
From: Dennis Young [mailto:DYoung@Brocade.COM]
Sent: Wednesday, February 19, 2003 6:48 PM
To: 'Buck Landry'; Lakshmi Ramasubramanian
Cc: ips@ece.cmu.edu
Subject: RE: iSCSI: Data In PDU with S bit set


In section 10.7 (draft 20):

   Status can accompany the last Data-in PDU if the command did not end
   with an exception (i.e., the status is "good status" - GOOD,
   CONDITION MET or INTERMEDIATE CONDITION MET).  The presence of
   status (and of a residual count) is signaled though the S flag bit.
   Although targets MAY choose to send even non-exception status in
   separate responses, initiators MUST support non-exception status in
   Data-In PDUs.

Based on the last sentence of the above paragraph, the initiator has
to be able to handle both cases, while the target has the option to
not send a separate response if there is no exception.

-Dennis

>-----Original Message-----
>From: Buck Landry [mailto:blandry@crossroads.com]
>Sent: Wednesday, February 19, 2003 5:18 PM
>To: Lakshmi Ramasubramanian
>Cc: ips@ece.cmu.edu; Julian_Satran@il.ibm.com
>Subject: RE: iSCSI: Data In PDU with S bit set
>
>
>Well, I don't see any explicit text (too bad), but..
>
>3.5.1.5 "the last SCSI Data-in PDU passed for a command may
>also contain the status if the status indicates termination
>with no exceptions (no sense or response involved)"
>
>.. implies (maybe just to me) that the SCSI task is terminated
>by a Data-In PDU w/S bit set.  A further response to a
>terminated task would be inappropriate methinks, unless you
>want to start talking about error recovery..
>
>Hope this helps, --buck
>
> -----Original Message-----
>From: Lakshmi Ramasubramanian [mailto:nramas@windows.microsoft.com]
>Sent: Wednesday, February 19, 2003 4:55 PM
>To: ips@ece.cmu.edu
>Subject: iSCSI: Data In PDU with S bit set
>
>
>If the target sends a Data In PDU with S bit set,
>can it also send a SCSI Response PDU for the same command?
>
>If the answer is no, there is no text in the spec that
>says a target should not send scsi response PDU.
>
>thanks!
> -lakshmi
>
>
>
>
>

------_=_NextPart_001_01C2D93C.9882CF90-- ------=_NextPartTM-000-d24540d5-4526-11d7-ac8c-009027aa5b50--