|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: aborting an out of sequence cmdSNI'd think option 1 is the simplest (with the caveat that the task mgmt PDU referred to is the Abort Task.) and only impacts the affected command/task. Pierre Labat and I have asked for this 4 months ago. (See : http://ips.pdl.cs.cmu.edu/mail/msg02958.html). The concept of connection allegiance should be extended to include the Abort Task. Also, connection allegiance should apply to the task (which spans multiple commands in the case of linked commands.), allowing for a deterministic clean up of stale PDUs of the task through the use of Abort Task. - Santosh Sandeep Joshi wrote: > > So our options for abort_task boil down to.. > (1) use connection allegiance for TASK MGMT PDU. > (2) reject all commands prior to cmdSN of TASK MGMT PDU. > (3) cmdSN of original task is sent with TASK MGMT PDU and > target at the iSCSI layer keeps state. > (4) iSCSI initiator retains state for deleted tasks to ensure > that R2T/Scsi Responses are appropriately handled. begin:vcard n:Rao;Santosh tel;work:408-447-3751 x-mozilla-html:FALSE org:Hewlett Packard, Cupertino.;SISL adr:;;19420, Homestead Road, M\S 43LN, ;Cupertino.;CA.;95014.;USA. version:2.1 email;internet:santoshr@cup.hp.com title:Software Design Engineer x-mozilla-cpt:;21088 fn:Santosh Rao end:vcard
Home Last updated: Tue Sep 04 01:05:01 2001 6315 messages in chronological order |