Return-Path: <owner-ips-outgoing@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h571iY306981
	for <ipsml@ece.cmu.edu>; Fri, 6 Jun 2003 21:44:34 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id ACC4898; Fri,  6 Jun 2003 21:44:33 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by hazard.ece.cmu.edu (Postfix) with ESMTP
	id 1BC6A93; Fri,  6 Jun 2003 21:44:31 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id D457F89DB; Fri,  6 Jun 2003 21:44:14 -0400 (EDT)
Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23])
	by sos.ece.cmu.edu (Postfix) with ESMTP id BA96C89D9
	for <ips-outgoing@sos.ece.cmu.edu>; Fri,  6 Jun 2003 21:44:14 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id 99F3582; Fri,  6 Jun 2003 21:44:14 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id 7904186; Fri,  6 Jun 2003 21:44:14 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by bache.ece.cmu.edu (Postfix) with ESMTP id 158F582
	for <ips-outgoing@ece.cmu.edu>; Fri,  6 Jun 2003 21:44:10 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id E052C89DC; Fri,  6 Jun 2003 21:44:09 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 4BD6289D9
	for <ips@sos.ece.cmu.edu>; Fri,  6 Jun 2003 21:44:08 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix)
	id DA64B97; Fri,  6 Jun 2003 21:44:07 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id B34A5B1; Fri,  6 Jun 2003 21:44:07 -0400 (EDT)
Received: from mail.ivivity.com (unknown [64.238.111.99])
	by osgood.ece.cmu.edu (Postfix) with ESMTP id 01F1997
	for <ips@ece.cmu.edu>; Fri,  6 Jun 2003 21:44:04 -0400 (EDT)
Received: by ATLOPS with Internet Mail Service (5.5.2653.19)
	id <2CY0TMM2>; Fri, 6 Jun 2003 21:44:03 -0400
Message-ID: <AEC4671C8179D61194DE0002B328BDD272FDE3@ATLOPS>
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
To: Rod Harrison <rod.harrison@windriver.com>, ips@ece.cmu.edu
Subject: RE: iscsi: Data PDU in two Sequence multiplexing issue
Date: Fri, 6 Jun 2003 21:44:02 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-12.1 required=5.0
	tests=BAYES_10,ORIGINAL_MESSAGE
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

I think the word "fulfilled" in 10.8 is the same as saying "completed".

T->I R2T-A
T->I R2T-B

So PDU 1 of A  -> PDU 1 of B -> PDU2 of A -> PDU2 of B would be illegal
because sequence A is not fulfilled before sequence B begins.

Do you agree with that?

Eddy


-----Original Message-----
From: Rod Harrison [mailto:rod.harrison@windriver.com] 
Sent: Friday, June 06, 2003 8:52 PM
To: Sanjay Goyal; ips@ece.cmu.edu
Subject: RE: iscsi: Data PDU in two Sequence multiplexing issue


That depends on why the initiator is sending the data. If we are
talking solely about unsolicited data then you are correct, all
the unsolicited data for command N must be sent before any
unsolicited data for command N+1. In your example we must see A1,
A2, B1, B2.

However, your second sequence can be valid if there are solicited
data involved. There are at least two valid scenarios for A1, B1,
A2, B2:

First A1 and B1 are unsolicited data and are FirstBurstSize big.
The initiator would then have to see R2T-A2 and R2T-B2 in that
order. Where R2T-A2 means the R2T requesting PDU A2.

Alternatively all the data could be solicited and A1 and B1
satisfy R2T-A1 and R2T-B1 respectively.

What 3.2.4.1 is telling you is that the target can not assume the
PDU following a command PDU is the corresponding unsolicited
data. In fact pretty much any PDU can come next, the only thing
that is guaranteed is that the next unsolicited DATA-OUT PDU will
be for command in question.

- Rod

-----Original Message-----
From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On
Behalf Of
Sanjay Goyal
Sent: Friday, June 06, 2003 12:58 PM
To: ips@ece.cmu.edu
Subject: iscsi: Data PDU in two Sequence multiplexing issue


Hi,
Can somebody please comment,

This is what I am not very clear about, from the specification.
-----------------
10.8 says: Within a connection, outstanding R2Ts MUST be
fulfilled by the initiator in the order in which they were
received.

3.2.4.1 says: When unsolicited data is used, the order of the
unsolicited
data on each connection MUST match the order in which the
commands
on that connection are sent. Command and unsolicited data PDUs
may
be interleaved on a single connection as long as the ordering
requirements of each are maintained (e.g., command N+1 MAY be
sent
before the unsolicited Data-Out PDUs for command N, but the
unsolicited Data-Out PDUs for command N MUST precede the
unsolicited
Data-Out PDUs of command N+1).
------------------


if we have two Data-out sequences A and B of 2 pdus each, to be
sent on the
same connection.
this is how I think they will be sent
PDU 1 of A -> PDU2 of A  -> PDU1 of B -> PDU2 of B
  What I am trying to verify is that the below sequence is valid
or not.
PDU 1 of A  -> PDU 1 of B -> PDU2 of A -> PDU2 of B

Regards
Sanjay Goyal


