Return-Path: <owner-ips-outgoing@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips-outgoing@ece.cmu.edu>
Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h4LKIT310399
	for <ipsml@ece.cmu.edu>; Wed, 21 May 2003 16:18:29 -0400 (EDT)
Received: by osgood.ece.cmu.edu (Postfix, from userid 953)
	id 9F60A9B; Wed, 21 May 2003 16:18:28 -0400 (EDT)
Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27])
	by osgood.ece.cmu.edu (Postfix) with ESMTP
	id BA76195; Wed, 21 May 2003 16:18:25 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id BCB8A8953; Wed, 21 May 2003 16:18:10 -0400 (EDT)
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id A92F98950
	for <ips-outgoing@sos.ece.cmu.edu>; Wed, 21 May 2003 16:18:10 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 76B9B7A; Wed, 21 May 2003 16:18:10 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 587337D; Wed, 21 May 2003 16:18:10 -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 B6E9F7A
	for <ips-outgoing@ece.cmu.edu>; Wed, 21 May 2003 16:18:05 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 9049E89D2; Wed, 21 May 2003 16:18:05 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23])
	by sos.ece.cmu.edu (Postfix) with ESMTP id C5E278950
	for <ips@sos.ece.cmu.edu>; Wed, 21 May 2003 16:18:03 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id 5FF6868; Wed, 21 May 2003 16:18:03 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id 3A95F76; Wed, 21 May 2003 16:18:03 -0400 (EDT)
Received: from lucy.trebia.com (lucy.trebia.com [65.192.191.151])
	by bache.ece.cmu.edu (Postfix) with ESMTP id 0C85568
	for <ips@ece.cmu.edu>; Wed, 21 May 2003 16:17:31 -0400 (EDT)
Received: from achadda (trebia-dhcp-30-56.trebia.com [192.168.30.56]) by lucy.trebia.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id L2PXH559; Wed, 21 May 2003 16:16:57 -0400
From: "Anshul Chadda" <anshul.chadda@trebia.com>
To: "Saikrishnan Krishnamurthy" <saikrishnan.krishnamurthy@qlogic.com>,
   <ips@ece.cmu.edu>
Subject: RE: Immediate Commands
Date: Wed, 21 May 2003 16:16:56 -0400
Message-ID: <LHEFKPDPACOJAKPDACKIGEIECDAA.anshul.chadda@trebia.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0000_01C31FB4.66106270"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <2A8D600C919D2D41A3DAA2D2FEC7171437D59B@homer.qlogic.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-13.8 required=5.0
	tests=BAYES_01,HTML_20_30,HTML_FONT_COLOR_BLUE,IN_REP_TO,
	      MSGID_GOOD_EXCHANGE
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C31FB4.66106270
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Immediate CommandsHi Sai:
I dont think there are any explicit restrictions on the initiator for
delivering immediate commands defined in the iSCSI spec. However, the target
restriction on immediate command handling (that you mentioned) gives an idea
to the initiator that if it has two outstanding immediate(one task mgt. and
one non-task mgt.) commands on a connection, they will successfully
complete. But if the initiator has more than two outstanding immediate
commands per connection, then there is no guarantee of successful completion
of the extra immediate commands by the target.

Hope this helps!!

Anshul
  -----Original Message-----
  From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf Of
Saikrishnan Krishnamurthy
  Sent: Wednesday, May 21, 2003 12:33 PM
  To: ips@ece.cmu.edu
  Subject: Immediate Commands


  Hi all,

          The iSCSI standard specifies immediate command handling (sec.
3.2.2.1) at the target and mandates the target to support atleast one
Immediate Task Mgmnt. and one Immediate non-Task Mgmnt. command "per
connection". This implies that initiators can have multiple (more than two)
outstanding Immediate commands to the same target on other connections (in
multiple connection scenario). Does the standard mandate any restriction on
the initiators in handling or delivering multiple immediate commands ??.



  Sai.

------=_NextPart_000_0000_01C31FB4.66106270
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Immediate Commands</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D005355919-21052003><FONT face=3DArial color=3D#0000ff =
size=3D2>Hi=20
Sai:</FONT></SPAN></DIV>
<DIV><SPAN class=3D005355919-21052003><FONT face=3DArial color=3D#0000ff =
size=3D2>I dont=20
think there are any explicit restrictions on&nbsp;the initiator for =
delivering=20
immediate commands defined in the iSCSI spec. However, the target =
restriction on=20
immediate command handling (that you mentioned)&nbsp;gives an idea to =
the=20
initiator that if it has two outstanding immediate(one task mgt. and one =

non-task mgt.) commands on a connection, they will successfully =
complete. But if=20
the initiator&nbsp;has more than two outstanding immediate commands per=20
connection, then there is no guarantee of successful completion of the =
extra=20
immediate commands&nbsp;by the target.</FONT></SPAN></DIV>
<DIV><SPAN class=3D005355919-21052003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D005355919-21052003><FONT face=3DArial color=3D#0000ff =
size=3D2>Hope=20
this helps!!</FONT></SPAN></DIV>
<DIV><SPAN class=3D005355919-21052003><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D005355919-21052003><FONT face=3DArial color=3D#0000ff =

size=3D2>Anshul</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
owner-ips@ece.cmu.edu=20
  [mailto:owner-ips@ece.cmu.edu]<B>On Behalf Of </B>Saikrishnan=20
  Krishnamurthy<BR><B>Sent:</B> Wednesday, May 21, 2003 12:33 =
PM<BR><B>To:</B>=20
  ips@ece.cmu.edu<BR><B>Subject:</B> Immediate =
Commands<BR><BR></FONT></DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3DArial size=3D2>Hi all,</FONT> </P>
  <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT face=3DArial =
size=3D2>The=20
  iSCSI standard specifies immediate command handling (sec. 3.2.2.1) at =
the=20
  target and mandates the target to support atleast one Immediate Task =
Mgmnt.=20
  and one Immediate non-Task Mgmnt. command "per connection". This =
implies that=20
  initiators can have multiple (more than two) outstanding Immediate =
commands to=20
  the same target on other connections (in multiple connection =
scenario). Does=20
  the standard mandate any restriction on the initiators in handling or=20
  delivering multiple immediate commands ??.</FONT></P><BR>
  <P><FONT face=3DArial size=3D2>Sai.</FONT> =
</P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0000_01C31FB4.66106270--

