Reservation checking
Mallikarjun C.
cbm at rose.hp.com
Mon May 6 18:54:13 PDT 2002
* From the T10 Reflector (t10 at t10.org), posted by:
* "Mallikarjun C." <cbm at rose.hp.com>
*
Ken,
> Is a task in the dormant state considered to be entered
> into the task set?
I'd say yes - because task attributes could have caused the
task to be in Dormant state, and task attribute considerations
would be applied only to tasks in the task set.
>I must
> perform reservation checking twice during the lifetime of
> a task.
That is certainly one way to interpret it.
Alternatively, one may conclude that the current text really
doesn't place a requirement on an implementation to *not*
enter a task w/ Reservation conflict into the Task set. IOW, it's
not saying "A task shall not be entered into a task set if the
following conditions exist - .....". If you go by this, you'd only
have to check once - when the task is a candidate for transitioning
into the Enabled state.
> "The requirements for task set management only apply to a
> task after it has been entered into a task set. A task
> shall be entered into a task set unless a condition exists
> that causes that task to be completed with a status of
> BUSY, RESERVATION CONFLICT, TASK SET FULL, or ACA ACTIVE."
--
Mallikarjun
Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions Organization
Hewlett-Packard MS 5668
Roseville CA 95747
cbm at rose.hp.com
----- Original Message -----
From: "Ken Craig" <kcraig at istor.com>
To: <t10 at t10.org>
Sent: Monday, May 06, 2002 4:49 PM
Subject: Reservation checking
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "Ken Craig" <kcraig at istor.com>
> *
> I asked this question last week but have seen
> no replies. That leads me to believe I didn't
> ask the question correctly so I'm trying again.
>
> SAM-2, Rev 22, 24 Jan. 2002, Section 7.1, last paragraph
> states
>
> "The requirements for task set management only apply to a
> task after it has been entered into a task set. A task
> shall be entered into a task set unless a condition exists
> that causes that task to be completed with a status of
> BUSY, RESERVATION CONFLICT, TASK SET FULL, or ACA ACTIVE."
>
> SPC-3, Rev 6, 5 April 2002, Section 5.5.1, page 29, last paragraph
> states
>
> "An unlinked command shall be checked for reservation
> conflicts before the task containing that command enters
> the enabled task state."
>
> My question is this.
>
> Is a task in the dormant state considered to be entered
> into the task set?
>
> My reading of the SAM-2 Task Set management rules leads me
> to believe that it is which leads me to believe that I must
> perform reservation checking twice during the lifetime of
> a task. Once before it's entered into the dormant state
> and secondly before a dormant task enters the enabled
> state.
>
> Thanks,
> Kenneth Ray Craig, Jr.
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
>
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org
More information about the T10
mailing list