|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: iSCSI: Abort Task Set CmdSN: < or <=
Tony,
Immediate commands are only partially ordered. It does not make too much
sense to have Task Management account for immediate commands
that are not completely ordered vs. the TM itself.
Abort Task Set should act only on commands that where issued before it and
immediate commands with the same CmdSN do not meet this criteria.
Julo
"Tony Battersby"
<tonyb@cybernetic To: <ips@ece.cmu.edu>
s.com> cc:
Sent by: Subject: iSCSI: Abort Task Set CmdSN: < or <=
owner-ips@ece.cmu
.edu
08/12/2002 11:39
PM
Please respond to
tonyb
Draft 15, section 9.5.1:
"Task management requests must act on all the commands having a CmdSN lower
than the task management CmdSN."
"... all the tasks covered by the Task Management response (i.e., with
CmdSN
not higher than the task management command CmdSN), ..."
"Lower than" is not the same as "not higher than" for the case of equal
CmdSN's, which could happen if an immediate command preceeded the task
management request. So if an immediate command is issued followed by a
Task
Management Function Request of ABORT TASK SET with the same CmdSN as the
immediate command, should the immediate command be aborted or not?
Anthony J. Battersby
Cybernetics
Home Last updated: Tue Aug 13 19:18:56 2002 11632 messages in chronological order |