Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h0U1rTv17378
	for ips-outgoing; Wed, 29 Jan 2003 20:53:29 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from palrel12.hp.com (palrel12.hp.com [156.153.255.237])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0U1rOW17366
	for <ips@ece.cmu.edu>; Wed, 29 Jan 2003 20:53:24 -0500 (EST)
Received: from rosemail.rose.hp.com (rosemail.rose.hp.com [15.96.64.26])
	by palrel12.hp.com (Postfix) with ESMTP
	id 3004E1C0221E; Wed, 29 Jan 2003 17:53:23 -0800 (PST)
Received: from swathi (swathi.rose.hp.com [15.43.213.237]) by rosemail.rose.hp.com with SMTP (8.7.1/8.7.3 SMKit7.02) id RAA24816; Wed, 29 Jan 2003 17:53:22 -0800 (PST)
Message-ID: <007101c2c802$5e3dbf70$edd52b0f@rose.hp.com>
From: "Mallikarjun C." <cbm@rose.hp.com>
To: "Bill Studenmund" <wrstuden@wasabisystems.com>, <ips@ece.cmu.edu>
References: <Pine.NEB.4.33.0301281434200.642-100000@candlekeep.home-net.internetconnect.net>
Subject: Re: iSCSI: different question about terminated tasks
Date: Wed, 29 Jan 2003 17:53:20 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

>My question is what do we do if there are multiple tasks with the
> NACA bit set? Do we initiate ACA for each of them, or only once?

This is not an iSCSI issue (please see SAM2r23, 5.8.1), but I'll offer
just my interpretation of SAM-2.  Also note that there's no formal model
in SAM-x for a SCSI transport layer to notify the SCSI application layer 
of a task termination due to transport dynamics.  The model (if and when 
one is spec'ed) would have to deal with the question of how the notification
affects that task even when the ACA is active (which is the specific scenario
you're describing).  I read SAM-2 (with the model caveat) as saying that 
there shall be one ACA for each terminated task today, if the task with the 
ACA attribute (the cleanup task) didn't cleanup those to-be-terminated tasks 
by then.

> Also, in the case of Logout Request, do we wait for all the tasks to go
> through ACA before sending the Logout Response?

That's not the intent of the "cleanup" wording in 10.15.  Dealing with ACA is a 
SCSI matter.  The "cleanup" refers to the requirement on the iSCSI layer to
cleanup all the iSCSI-level task and connection resources associated with the 
iSCSI connection (along with the task termination notifications, whose after-effects 
SCSI will deal with), before sending a successful Logout Response.

Hope that helps.
--
Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions
Hewlett-Packard MS 5668 
Roseville CA 95747
cbm@rose.hp.com

----- Original Message ----- 
From: "Bill Studenmund" <wrstuden@wasabisystems.com>
To: <ips@ece.cmu.edu>
Sent: Tuesday, January 28, 2003 4:21 PM
Subject: iSCSI: different question about terminated tasks


> I have a question related to the terminated task thread we had.
> 
> When we terminate SCSI tasks for the reasons mentioned in the thread
> (10.14.5 in draft 20), and they have the NACA bit set, we will establish
> ACA. My question is what do we do if there are multiple tasks with the
> NACA bit set? Do we initiate ACA for each of them, or only once?
> 
> Also, in the case of Logout Request, do we wait for all the tasks to go
> through ACA before sending the Logout Response? The text which encourages
> this question is the first paragraph of 10.15:
> 
>    The logout response is used by the target to indicate if the cleanup
>    operation for the connection(s) has completed.
> 
> 
> Thanks!
> 
> Take care,
> 
> Bill
> 
> 

