Re: [Ips] Data-In ExpDataSN

<Black_David@emc.com> Fri, 25 September 2009 14:44 UTC

Return-Path: <Black_David@emc.com>
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 999A23A6965 for <ips@core3.amsl.com>; Fri, 25 Sep 2009 07:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCm96nPC4VMr for <ips@core3.amsl.com>; Fri, 25 Sep 2009 07:44:30 -0700 (PDT)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id AD90E3A6923 for <ips@ietf.org>; Fri, 25 Sep 2009 07:44:30 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.3.2/Switch-3.1.7) with ESMTP id n8PEjbbX031973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Sep 2009 10:45:37 -0400
Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.16]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 25 Sep 2009 10:43:45 -0400
Received: from corpussmtp2.corp.emc.com (corpussmtp2.corp.emc.com [128.221.166.45]) by mailhub.lss.emc.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id n8PEhiTD017263; Fri, 25 Sep 2009 10:43:45 -0400
Received: from CORPUSMX80A.corp.emc.com ([10.254.89.202]) by corpussmtp2.corp.emc.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 25 Sep 2009 10:43:44 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA3DEE.953F5EFA"
Date: Fri, 25 Sep 2009 10:43:44 -0400
Message-ID: <9FA859626025B64FBC2AF149D97C944A03E1E901@CORPUSMX80A.corp.emc.com>
In-Reply-To: <298d852f0909242330o15ff44bdg85c0c436ad603755@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Ips] Data-In ExpDataSN
Thread-Index: Aco9qdLymljwXPfKQIeFgtXkkUBNRAAQb4IA
References: <298d852f0909242330o15ff44bdg85c0c436ad603755@mail.gmail.com>
From: Black_David@emc.com
To: yusunn@gmail.com, ips@ietf.org
X-OriginalArrivalTime: 25 Sep 2009 14:43:44.0773 (UTC) FILETIME=[952CC350:01CA3DEE]
X-EMM-EM: Active
Subject: Re: [Ips] Data-In ExpDataSN
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2009 14:44:31 -0000

> RFC 3720 says that Data-In/R2T PDU number is acknowledged by ExpDataSN
filed of SCSI Response 
 
Where?  Section 3.2.2.3 says:
    Data and R2T PDUs are implicitly acknowledged by status for the
command.

> But if a target choose to send a Data-In PDU with S bit set instead of
a SCSI Response .
> Where to get the ExpDataSN ? There is no such a field in Data-In PDU.

Not by that name, but the information is present.  The ExpDataSN
field in the SCSI Response PDU is "The number of R2T and Data-In
(read) PDUs the target has sent for the command."  That number can
be obtained from a Data-In PDU whose S bit is set to 1 by adding 1
to the value of that PDU's DataSN field.

Thanks,
--David


 



________________________________

	From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On
Behalf Of yushang
	Sent: Friday, September 25, 2009 2:31 AM
	To: ips@ietf.org
	Subject: [Ips] Data-In ExpDataSN
	
	
	Dear all , RFC 3720 says that Data-In/R2T PDU number is
acknowledged by ExpDataSN filed of SCSI Response . But if a target
choose to send a Data-In PDU with S bit set instead of a SCSI Response .
Where to get the ExpDataSN ? There is no such a field in Data-In PDU.
Many thanks.