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 h1KMHSj01722 for ips-outgoing; Thu, 20 Feb 2003 17:17:28 -0500 (EST) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from mail15.messagelabs.com (mail15.messagelabs.com [63.210.62.243]) by ece.cmu.edu (8.11.0/8.10.2) with SMTP id h1K2loW19073 for ; Wed, 19 Feb 2003 21:47:50 -0500 (EST) X-VirusChecked: Checked X-Env-Sender: DYoung@Brocade.COM X-Msg-Ref: server-14.tower-15.messagelabs.com!1045709257!805 Received: (qmail 15934 invoked from network); 20 Feb 2003 02:47:38 -0000 Received: from sj6-b.brocade.com (HELO discus.brocade.com) (63.121.140.220) by server-14.tower-15.messagelabs.com with SMTP; 20 Feb 2003 02:47:38 -0000 Received: from hq-ex-c2.brocade.com (hq-ex-c2.brocade.com [192.168.126.35]) by discus.brocade.com (Postfix) with ESMTP id 65D2B4F61B; Wed, 19 Feb 2003 18:46:39 -0800 (PST) Received: by hq-ex-c2.brocade.com with Internet Mail Service (5.5.2653.19) id ; Wed, 19 Feb 2003 18:47:42 -0800 Message-ID: <7D17958F8536B640885BE12A446D548F02E6F1@hq-ex-4.brocade.com> From: Dennis Young To: "'Buck Landry'" , Lakshmi Ramasubramanian Cc: ips@ece.cmu.edu Subject: RE: iSCSI: Data In PDU with S bit set Date: Wed, 19 Feb 2003 18:47:40 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2D88A.6F1FD9C0" 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. ------_=_NextPart_001_01C2D88A.6F1FD9C0 Content-Type: text/plain; charset="iso-8859-1" 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_01C2D88A.6F1FD9C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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.micro= soft.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_01C2D88A.6F1FD9C0--