RE: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands

wrstuden@wasabisystems.com Mon, 02 February 2004 20:10 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06104 for <ips-archive@odin.ietf.org>; Mon, 2 Feb 2004 15:10:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnkOF-0008Oz-4h for ips-archive@odin.ietf.org; Mon, 02 Feb 2004 15:09:51 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i12K9p48032291 for ips-archive@odin.ietf.org; Mon, 2 Feb 2004 15:09:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnkOE-0008Ok-R7 for ips-web-archive@optimus.ietf.org; Mon, 02 Feb 2004 15:09:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06058 for <ips-web-archive@ietf.org>; Mon, 2 Feb 2004 15:09:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnkOB-0003it-00 for ips-web-archive@ietf.org; Mon, 02 Feb 2004 15:09:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnkNG-0003eE-00 for ips-web-archive@ietf.org; Mon, 02 Feb 2004 15:08:51 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AnkMV-0003Yr-00 for ips-web-archive@ietf.org; Mon, 02 Feb 2004 15:08:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnkMT-0007YW-Lx; Mon, 02 Feb 2004 15:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AnkMK-0007Sg-89 for ips@optimus.ietf.org; Mon, 02 Feb 2004 15:07:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05832 for <ips@ietf.org>; Mon, 2 Feb 2004 15:07:48 -0500 (EST)
From: wrstuden@wasabisystems.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AnkMH-0003Xr-00 for ips@ietf.org; Mon, 02 Feb 2004 15:07:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AnkLN-0003TE-00 for ips@ietf.org; Mon, 02 Feb 2004 15:06:54 -0500
Received: from mononoke.wasabisystems.com ([151.199.66.145]) by ietf-mx with esmtp (Exim 4.12) id 1AnkKg-0003Nr-00; Mon, 02 Feb 2004 15:06:10 -0500
Received: by mononoke.wasabisystems.com (Postfix, from userid 1021) id E4BA340167; Mon, 2 Feb 2004 15:06:09 -0500 (EST)
Date: Mon, 02 Feb 2004 12:05:56 -0800
X-X-Sender: wrstuden@neverwinter.home-net.icnt.net
To: Ramesh Mangamuri <rmangamuri@istor.com>
Cc: pat_thaler@agilent.com, Julian_Satran@il.ibm.com, cbm@rose.hp.com, ips@ietf.org, ips-admin@ietf.org
Subject: RE: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
In-Reply-To: <7D036BD3216A084DB1BD9D62BCEAF290570DD1@mail1irv.inside.istor.com>
Message-ID: <Pine.NEB.4.53.0402021118370.1174@neverwinter.home-net.icnt.net>
References: <7D036BD3216A084DB1BD9D62BCEAF290570DD1@mail1irv.inside.istor.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: ips-admin@ietf.org
Errors-To: ips-admin@ietf.org
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Id: IP Storage <ips.ietf.org>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60

On Mon, 2 Feb 2004, Ramesh Mangamuri wrote:

> To be honest I really don't know about the resources we would be saving
> by combining R2TSN and DataSN into one variable in the of bidirectional
> . But from logical standpoint, Pat's suggestion makes perfect sense to
> me.

I think the reason they are the same variable is that they (R2T numbers
and DataSN) are in the same number space, due to how SNACK Requests work.
To request a given DataSN or a given R2T be retransmitted, the initiator
sends a SNACK Request of Type 0. That's a Type 0 for _either_ a R2T or
DataSN retransmit. So for the target to keep things clear, it has to use
the same number space for both.

I think separating the number spaces would be ok, but it means changing
SNACK requests so that BiDi commands can tell what's being asked for.

Take care,

Bill

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www1.ietf.org/mailman/listinfo/ips