Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id h2DMKY307852 for ips-outgoing; Thu, 13 Mar 2003 17:20:34 -0500 (EST) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from mail.ivivity.com ([64.238.111.99]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h2DMKVM07844 for ; Thu, 13 Mar 2003 17:20:31 -0500 (EST) Received: by ATLOPS with Internet Mail Service (5.5.2653.19) id <1TWQJY8X>; Thu, 13 Mar 2003 17:20:30 -0500 Message-ID: From: Eddy Quicksall To: Buck Landry , ips@ece.cmu.edu Subject: RE: iSCSI: two CmdSN gap questions Date: Thu, 13 Mar 2003 17:20:29 -0500 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 For multiple connections, ABORT TASK should always have the I bit set. Otherwise you can get into a dead lock. Eddy -----Original Message----- From: Buck Landry [mailto:blandry@crossroads.com] Sent: Thursday, March 13, 2003 4:47 PM To: ips@ece.cmu.edu Subject: iSCSI: two CmdSN gap questions I'll try to keep this short. 1) Is ABORT TASK the only Task Management Function Request type that can be used to plug a CmdSN gap? (I'd assume "yes") 2) I assume ABORT TASKs that plug a gap should be sent w/immediate bit set. Otherwise, a target wouldn't consider the ABORT TASK for execution until after the missing command itself (3.2.2.1 ".. the iSCSI target layer MUST deliver the commands for execution in the order specified by CmdSN"). Do I misunderstand this? Thanks for any clarification, --buck